Bug#558930: marked as done (Resolve unresolved symbols in shared libraries)
Your message dated Thu, 3 Dec 2009 20:45:33 +0100
with message-id <20091203194533.GA30034@radis.liafa.jussieu.fr>
and subject line Re: Bug#558930: Resolve unresolved symbols in shared libraries
has caused the Debian Bug report #558930,
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 owner@bugs.debian.org
immediately.)
--
558930: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558930
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: libxmu
Version: 2:1.0.4-2
Severity: wishlist
User: peter.fritzsche@gmx.de
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/pkgreport.cgi?users=peter.fritzsche@gmx.de;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 XrmSetDatabase used by debian/libxmu6/usr/lib/libXmu.so.6.2.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol XCreatePixmap used by debian/libxmu6/usr/lib/libXmu.so.6.2.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol XFillRectangle used by debian/libxmu6/usr/lib/libXmu.so.6.2.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol XInternAtom used by debian/libxmu6/usr/lib/libXmu.so.6.2.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol XGetErrorDatabaseText used by debian/libxmu6/usr/lib/libXmu.so.6.2.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol XFreeColormap used by debian/libxmu6/usr/lib/libXmu.so.6.2.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol XRecolorCursor used by debian/libxmu6/usr/lib/libXmu.so.6.2.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol XDeleteProperty used by debian/libxmu6/usr/lib/libXmu.so.6.2.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol XGrabServer used by debian/libxmu6/usr/lib/libXmu.so.6.2.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol XGetGCValues used by debian/libxmu6/usr/lib/libXmu.so.6.2.0 found in none of the libraries.
dpkg-shlibdeps: warning: 58 other similar warnings have been skipped (use -v to see them all).
--- End Message ---
--- Begin Message ---
Version: 2:1.0.5-1
On Mon, Nov 30, 2009 at 19:32:37 +0100, Peter Fritzsche wrote:
> dpkg-shlibdeps: warning: symbol XrmSetDatabase used by debian/libxmu6/usr/lib/libXmu.so.6.2.0 found in none of the libraries.
> dpkg-shlibdeps: warning: symbol XCreatePixmap used by debian/libxmu6/usr/lib/libXmu.so.6.2.0 found in none of the libraries.
> dpkg-shlibdeps: warning: symbol XFillRectangle used by debian/libxmu6/usr/lib/libXmu.so.6.2.0 found in none of the libraries.
[...]
This got fixed upstream in 1.0.5.
Cheers,
Julien
--- End Message ---
Reply to: