Hello Peter, * Peter Volkov wrote on Tue, Jul 24, 2007 at 02:29:19PM CEST: > > I found the following problem that I'm not sure how to resolve. Consider > the following situation: in package wireshark there are program tshark > and library libwireshark. tshark is linked with libwireshark. Now, > during compilation tshark is called to generate some package > documentation, and here the problem arise: during this call dynamic > linker links tshark with installed on the > system /usr/lib/libwireshark.so.0 instead of library which was build > with the package itself. If I export LD_RUN_PATH everything works > correctly, but are there better ways? How can I tell libtool to link > program with the library from the package itself until I have not > installed it?
Typically this just works; it's one of Libtool's features. Are you using GNU Libtool or a modified version of it (say, Debian's)? I don't know whether Gentoo enables `link_all_deplibs=no'; see ./libtool --config | grep link_all_deplibs to find out. If yes, then you have just stumbled over a known bug of this modification, which is why it's not part of GNU Libtool yet. If my hypothesis is wrong, I'd like to see output of ./libtool --config as well as contents of Makefile.am's involved in building the libraries and the program, and the output (of the last command only) of this, done in a configured build tree: make -k find . -name \*.la | xargs ./libtool --mode=clean rm -f make Thanks, Ralf _______________________________________________ http://lists.gnu.org/mailman/listinfo/libtool
