Re: Some dpkg-cross issues
-----BEGIN PGP SIGNED MESSAGE-----
> > Shouldn't shlibs.local be used in this case instead of games with
> > LD_LIBRARY_PATH?
> For my problem situation no shlibs.local file exists nor one will be
> Only dh_makeshlibs is used to create debian/*/DEBIAN/shlibs but this is
> not shlibs.local and does not address the dh_shlibdeps -l<somewhere>
As far as I understand things, dpkg_shlibdeps should find out which
packages provide shared libraries required for given binaries.
In shlibs.local this information (which package will provide a library) may
be given for libraries that are builng built in the current (source)
How could you use and path information to get package names?
dh_shlibdeps "-l" key is needed only because original dpkg-shlibdeps uses
ldd. For dpkg-shlibdeps using objdump, this key does not provide any
useful ibnformation. Key that does is "-L", that provides package name.
Just looked at dh_shlibdeps sources. When called with -L, it calls
dpkg-shlibdeps with "-L debian/xxx/DEBIAN/shlibs", causing use of that
file as shlibs.local
So if you call dh_shlibdeps with proper -Lpackage key, and after
dh_makeshlibs, current dpkg-shlibdeps wrapper should work as is (unless
Or probably I'm misunderstanding something?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
-----END PGP SIGNATURE-----