Your message dated Tue, 22 May 2012 00:35:25 +0300
with message-id <[email protected]>
and subject line -lpthread missing was already fixed in cxxtools 2.0
has caused the Debian Bug report #558849,
regarding Resolve unresolved symbols in shared libraries
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
558849: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558849
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: cxxtools
Version: 1.4.8-3
Severity: wishlist
User: [email protected]
Usertags: unresolved-symbols-so
I build all packages some time ago with binutils-gold and your package build
without an hard failure, but I noticed that you seems to provide a library in
a specific library package so other packages can link against it without
problems.... but your shared object has still some unresolved symbols which
the program which links agaomst it must resolve. This isnt a good idea because
when you introduce new dependencies the package previously linked against the
old version will break because it doesnt know about the new dependency.
Maybe you could link against all needed libraries so programs must not link
against libraries which it doesnt need to use.
Maybe it is related to following bugs which hard failed due to unresolved
symbols in programs
http://bugs.debian.org/cgi-bin/[email protected];tag=no-add-needed
More informations can be found at
http://wiki.debian.org/qa.debian.org/FTBFS#A2009-11-02Packagesfailingbecausebinutils-gold.2BAC8-indirectlinking
dpkg-shlibdeps already showed you the related warnings:
dpkg-shlibdeps: warning: symbol sem_post used by
debian/libcxxtools6/usr/lib/libcxxtools.so.6.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol pthread_join used by
debian/libcxxtools6/usr/lib/libcxxtools.so.6.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol pthread_create used by
debian/libcxxtools6/usr/lib/libcxxtools.so.6.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol sem_getvalue used by
debian/libcxxtools6/usr/lib/libcxxtools.so.6.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol pthread_rwlock_destroy used by
debian/libcxxtools6/usr/lib/libcxxtools.so.6.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol sem_wait used by
debian/libcxxtools6/usr/lib/libcxxtools.so.6.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol pthread_kill used by
debian/libcxxtools6/usr/lib/libcxxtools.so.6.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol pthread_rwlock_rdlock used by
debian/libcxxtools6/usr/lib/libcxxtools.so.6.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol sem_trywait used by
debian/libcxxtools6/usr/lib/libcxxtools.so.6.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol pthread_rwlock_wrlock used by
debian/libcxxtools6/usr/lib/libcxxtools.so.6.0.0 found in none of the libraries.
--- End Message ---
--- Begin Message ---
Version: 2.0-1
Looks like this was already fixed with cxxtools 2.0. I'm closing it
now.
--- End Message ---
