Your message dated Sun, 29 Dec 2013 15:38:02 +1100
with message-id <1698926.gm72zrevPb@acer>
and subject line Re: Bug#558874: Resolve unresolved symbols in shared libraries
has caused the Debian Bug report #558874,
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.)
--
558874: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558874
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: libcommoncpp2
Version: 1.7.3-1
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 pthread_join used by
debian/libccgnu2-1.7-0/usr/lib/libccgnu2-1.7.so.0.0.3 found in none of the
libraries.
dpkg-shlibdeps: warning: symbol pthread_key_delete used by
debian/libccgnu2-1.7-0/usr/lib/libccgnu2-1.7.so.0.0.3 found in none of the
libraries.
dpkg-shlibdeps: warning: symbol pthread_rwlock_destroy used by
debian/libccgnu2-1.7-0/usr/lib/libccgnu2-1.7.so.0.0.3 found in none of the
libraries.
dpkg-shlibdeps: warning: symbol pthread_mutexattr_init used by
debian/libccgnu2-1.7-0/usr/lib/libccgnu2-1.7.so.0.0.3 found in none of the
libraries.
dpkg-shlibdeps: warning: symbol pthread_mutexattr_destroy used by
debian/libccgnu2-1.7-0/usr/lib/libccgnu2-1.7.so.0.0.3 found in none of the
libraries.
dpkg-shlibdeps: warning: symbol pthread_rwlock_tryrdlock used by
debian/libccgnu2-1.7-0/usr/lib/libccgnu2-1.7.so.0.0.3 found in none of the
libraries.
dpkg-shlibdeps: warning: symbol pthread_getspecific used by
debian/libccgnu2-1.7-0/usr/lib/libccgnu2-1.7.so.0.0.3 found in none of the
libraries.
dpkg-shlibdeps: warning: symbol pthread_rwlock_wrlock used by
debian/libccgnu2-1.7-0/usr/lib/libccgnu2-1.7.so.0.0.3 found in none of the
libraries.
dpkg-shlibdeps: warning: symbol pthread_rwlock_init used by
debian/libccgnu2-1.7-0/usr/lib/libccgnu2-1.7.so.0.0.3 found in none of the
libraries.
dpkg-shlibdeps: warning: symbol pthread_rwlock_unlock used by
debian/libccgnu2-1.7-0/usr/lib/libccgnu2-1.7.so.0.0.3 found in none of the
libraries.
dpkg-shlibdeps: warning: 15 other similar warnings have been skipped (use -v to
see them all).
--- End Message ---
--- Begin Message ---
Version: 1.8.0-1
On Mon, 30 Nov 2009 19:32:35 Peter Fritzsche wrote:
> 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.
Thanks Peter,
I believe this has been resolved since the upload of version 1.8:
https://buildd.debian.org/status/fetch.php?pkg=libcommoncpp2&arch=ia64&ver=1.8.0-1&stamp=1269544266
Mark
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
