Hi, On Thu, 24 Jan 2008, Matthias Klose wrote: > Currently dpkg-shlibdeps emits wrong-leading warnings for packages > linked against libgcj_bc.so: > > dpkg-shlibdeps: warning: debian/ecj-gcj/usr/bin/ecj-gcj shouldn't be linked > with libgcj_bc.so.1 (it uses none of its symbols). > dpkg-shlibdeps: warning: debian/ecj-gcj/usr/bin/ecj-gcj shouldn't be linked > with libpthread.so.0 (it uses none of its symbols). > dpkg-shlibdeps: warning: debian/ecj-gcj/usr/bin/ecj-gcj shouldn't be linked > with librt.so.1 (it uses none of its symbols). > dpkg-shlibdeps: warning: debian/ecj-gcj/usr/bin/ecj-gcj shouldn't be linked > with libz.so.1 (it uses none of its symbols). > dpkg-shlibdeps: warning: debian/ecj-gcj/usr/bin/ecj-gcj shouldn't be linked > with libdl.so.2 (it uses none of its symbols). > > If libgcj_bc.so.1 is found as a dependency, only the symbols built > from the libgcj_bc.c file should be evaluated.
Sorry, I don't understand what you mean. Can you give some more details? The only thing that I special case currently is libm which is auto-added by g++ thus I don't display that warning for binaries that do also link against libstdc++. I fail to see the same logic here. Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/
