Howard Chu wrote:
Michael Ströder wrote:
Howard Chu wrote:
If you didn't do anything special then the build will use the libtool scripts bundled in the source tree.
My mistake, the libtool wrapper script doesn't use LD_LIBRARY_PATH, it actually relinks the binary.
And what can I do about it?
Things like this can lead to a bunch of errornous ITS reports.
Only if you already have a fairly broken build environment. Notice that the installed binaries have a different soname from the build binaries:
% ls /usr/lib/libl{dap,ber}* /usr/lib/liblber-2.4.so.2 /usr/lib/libldap_r-2.4.so.2 /usr/lib/liblber-2.4.so.2.1.0 /usr/lib/libldap_r-2.4.so.2.1.0 /usr/lib/liblber.a /usr/lib/libldap_r.a /usr/lib/liblber.so /usr/lib/libldap_r.so /usr/lib/libldap-2.4.so.2 /usr/lib/libldap.so /usr/lib/libldap.a
% find . -name '*.so.*' ./libldap_r/.libs/libldap_r-2.4-releng.so.2 ./libldap_r/.libs/libldap_r-2.4-releng.so.2.4.1 ./liblber/.libs/liblber-2.4-releng.so.2.4.1 ./liblber/.libs/liblber-2.4-releng.so.2 ./libldap/.libs/libldap-2.4-releng.so.2 ./libldap/.libs/libldap-2.4-releng.so.2.4.1
There's no way it should ever be using your installed libraries when all of the built binaries are using the "-releng" tag in their soname.
1. When Quanah announces that RE24 is tagged and ready for release "-releng" is already removed.
2. It's my strong opinion that if someone unpacks a release tar.gz and builds it running "make test" should not conflict with an already installed version of /usr/lib/libl{dap,ber}*. It's quite normal that you build and test before installing the next release. Isn't it? Having a separate build system without any pre-installed libldap is nearly impossible today. On openSUSE even the software installation tool zypper has a dependency on libldap.
Ciao, Michael.