On Fri, 29 Dec 2000, Adam Heath wrote: > Nononononono. You are confused.
> LD_LIBRARY_PATH is used so that programs and libs in debian/tmp that are > compiled AGAINST libs in debian/tmp can be properly resolved with ldd. > debian/shlibs.local is then used to map the libraries to packages. > debian/shlibs.local can be used to override the system > (/var/lib/dpkg/info/*.shlibs) shlibs files. > There are 2 things going on, and both are needed. I guess I can't see a case where debian/shlibs.local is still needed if LD_LIBRARY_PATH is properly set, but I'll take your word for it. In any case, empirical testing shows that when a program is linked against libs in debian/tmp/, LD_LIBRARY_PATH is both necessary and sufficient to make dpkg-shlibdeps happy. Steve Langasek postmodern programmer
