> On Tue, Jan 24, 2006 at 06:43:02PM +0300, Nikita V. Youshchenko wrote: > > dpkg-shlibdeps calls ldd, which will just fail if LD_LIBRARY_PATH > > won't point to directories with local libraries. > > That's not true. ldd will just happily print "libfoo.so.1 => not found" > and exit with exit code 0. So this doesn't terminate dpkg-shlibdeps.
Hmm... New information for me. I was sure that ldd, as any other [good-behaving] unix utility, exits with non-zero status on errors. A bug in ldd? But if ldd does not dislike unresolved libraries, I see no other problems with dropping -l. Library files from non-standard paths won't be found by dpkg anyway, so can't be processed in way other than shlibs.local In this sence, new information that comes from ldd finding libraries in LD_LIBRARY_PATH dirs, is useless. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]