Howard Chu wrote: > Michael Ströder wrote: >> >> Does setting LD_LIBRARY_PATH in tests/scripts/defines.sh have any effect? > > Not any more. It used to, when we were using a much older version of > libtool. The current version of libtool that we use sets LD_LIBRARY_PATH > in the wrapper script that it generates for each dynamically linked > binary that it produces, so that line in defines.sh is obsolete.
Hmm... > Are you using a different version of libtool? How can I find out? I didn't specify anything special. However there is a libtool package installed: # rpm -qf `which libtool` libtool-2.2.6-1.20 See excerpts of config.log below. Ciao, Michael. -------------------------------- snip -------------------------------- [..] configure: In function 'main': configure:11224: warning: incompatible implicit declaration of built-in function 'exit' configure:11231: $? = 0 configure:11249: result: yes configure:11272: checking if libtool supports shared libraries configure:11274: result: yes configure:11277: checking whether to build shared libraries configure:11298: result: yes configure:11301: checking whether to build static libraries configure:11305: result: yes configure:11397: creating libtool configure:12458: checking how to run the C preprocessor configure:12574: result: cc -E configure:12603: cc -E -I/usr/include -I/usr/include -I/usr/include -I/usr/include -DDEVEL conftest.c configure:12609: $? = 0 configure:12640: cc -E -I/usr/include -I/usr/include -I/usr/include -I/usr/include -DDEVEL conftest.c conftest.c:26:28: error: ac_nonexistent.h: No such file or directory configure:12646: $? = 1 [..] LIBTOOL='$(SHELL) $(top_builddir)/libtool'
