[Date Prev][Date Next] [Chronological] [Thread] [Top]

(ITS#3734) upgrade to 2.2 on a box with 2.1 installed causes new binaries to be linked against old libs

Full_Name: Robin H. Johnson
Version: 2.2.26
OS: Gentoo Linux
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (

If you have 2.1 installed on your machine, and then compile 2.2.26, the new
binaries (ldapsearch et al) are linked to the OLD libaries as well as the new

x29 / # ldd /usr/bin/ldapsearch
        linux-gate.so.1 =>  (0xffffe000)
        libldap-2.2.so.7 => /usr/lib/libldap-2.2.so.7 (0xb7f90000)
        liblber-2.2.so.7 => /usr/lib/liblber-2.2.so.7 (0xb7f82000)
        libssl.so.0.9.7 => /usr/lib/libssl.so.0.9.7 (0xb7f51000)
        libcrypto.so.0.9.7 => /usr/lib/libcrypto.so.0.9.7 (0xb7e4d000)
        libcrypt.so.1 => /lib/libcrypt.so.1 (0xb7e1f000)
        libresolv.so.2 => /lib/libresolv.so.2 (0xb7e0a000)
        libc.so.6 => /lib/tls/libc.so.6 (0xb7cdd000)
        liblber.so.2 => not found
        libdl.so.2 => /lib/libdl.so.2 (0xb7cd8000)
        /lib/ld-linux.so.2 (0xb7fea000)

This means the new binaries cannot be run, as they try to load the old liblber
when you run them.
if you then make clean and compile again (after installing 2.2 for the first
time), the binaries are then compiled properly.