On Tue, Sep 19, 2000 at 12:48:18AM +0200, Daniele Cruciani wrote:
> dh_shlibdeps -l/usr/lib/mozilla
> dpkg-shlibdeps: warning: unknown output from ldd on 
> `debian/tmp/usr/bin/galeon-bin': `        libgtkembedmoz.so => 
> /usr/lib/mozilla/libgtkembedmoz.so (0x40505000)'
> dpkg-shlibdeps: warning: unknown output from ldd on 
> `debian/tmp/usr/bin/galeon-bin': `        libplds4.so => /usr/lib/libplds4.so 
> (0x40526000)'
> dpkg-shlibdeps: warning: unknown output from ldd on 
> `debian/tmp/usr/bin/galeon-bin': `        libplc4.so => /usr/lib/libplc4.so 
> (0x4052a000)'
> dpkg-shlibdeps: warning: unknown output from ldd on 
> `debian/tmp/usr/bin/galeon-bin': `        libnspr4.so => /usr/lib/libnspr4.so 
> (0x4052f000)'
> dpkg-shlibdeps: warning: unknown output from ldd on 
> `debian/tmp/usr/bin/galeon-bin': `        libgtksuperwin.so => 
> /usr/lib/mozilla/libgtksuperwin.so (0x40572000)'
> dpkg-shlibdeps: warning: unknown output from ldd on 
> `debian/tmp/usr/bin/galeon-bin': `        libxpcom.so => 
> /usr/lib/mozilla/libxpcom.so (0x40576000)'

Resolving this depends on whether Galeon is something that's usually
tightly linked with Mozilla - it seems to be using its private .so's.

If yes, then you should ignore this and set a strong manual dependency on
mozilla in galeon's Depends: line.

If not, Mozilla needs to export some of its libraries to a non-private
directory, or just make symbolic links e.g. /usr/lib/libxpcom.so ->
mozilla/libxpcom.so etc.

Back when I maintained mozilla, libpldsX.so and libplcX.so were shared
libraries, made from NSPR sources, and were distributed in libnsprX package.
I'm not sure why this changed...

> dpkg-shlibdeps: warning: unable to find dependency information for shared 
> library /usr/lib/libfakeroot/libfakeroot (soname 0, path 
> /usr/lib/libfakeroot/libfakeroot.so.0, dependency field Depends)

This is bad, and it shouldn't have happened, as you shouldn't be linking to
libfakeroot while building a normal package...

-- 
Digital Electronic Being Intended for Assassination and Nullification

Reply via email to