Bug#558932: Resolve unresolved symbols in shared libraries
Source: lineakd
Version: 1:0.9-6
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 dlsym used by debian/liblineak-0.9-0/usr/lib/liblineak-0.9.so.0.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol dlclose used by debian/liblineak-0.9-0/usr/lib/liblineak-0.9.so.0.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol dlopen used by debian/liblineak-0.9-0/usr/lib/liblineak-0.9.so.0.0.0 found in none of the libraries.
dpkg-shlibdeps: warning: symbol dlerror used by debian/liblineak-0.9-0/usr/lib/liblineak-0.9.so.0.0.0 found in none of the libraries.
Reply to: