Re: Some dpkg-cross issues
> dpkg-shlibdeps.orig uses ldd, so it's behaviour depends on
> LD_LIBRARY_PATH value.
> dpkg-shlibdeps uses objdump, so it is no affected by LD_LIBRARY_PATH
Yes this is the point.
> Could you please provide an example that relies dh_shlibdeps -l, so we
> could look what exactly for it is used, and decide how dpkg-cross should
> handle it (if it should)?
The example whould be a multi-binary package with library and a application
that depends on this library. But instead make a full bug report I will fix
it and provide a patch. I think this would be the simpler... I will consider
LD_LIBRARY_PATH too while searching for the package.
> This means that instead of diverting dh_strip, we should ensure that strip
> that is in path can handle non-native binaries.
This would be the all-purpose solution for now and future.
> Isn't it better to make setup_cross_env() to do necessary quoting?
Yes it would be. I'm today not sure what to quote. Maybe I should check
sources from distcc or ccache doing the same.