[Date Prev][Date Next]
Build: 2.1.13 under SuSE Linux 8.0 with both BDB 4.0 and 4.1 (ITS#2339)
Full_Name: Peter A. Savitch
OS: SuSE Linux 8.0
Submission from: (NULL) (220.127.116.11)
I'm using SuSE 8.0 which has a lot of RPM packages dependent on BDB 4.0,
including cyrus-sasl. So I can not remove db-4.0 from my system without damage.
Though I can install both 4.0/4.1 shared libraries with headers/statics from 4.1
to satisfy OpenLDAP configure script. I've made custom RPMs.
The latest SuSE Linux distribution (8.1) has the same thing with BDB 4.0.
I've tried to make a separate cyrus-sasl build with libdb-4.1.so link. Sasl
builds okay while both libdb-4.0.so and libdb-4.1.so installed in /usr/lib:
# ls -l /usr/lib/libdb*.so
/usr/lib/libdb-4.so -> libdb-4.0.so
/usr/lib/libdb.so -> libdb-4.1.so
/usr/lib/libdb1.so -> ../../lib/libdb.so.2
/usr/lib/libdb2.so -> ../../lib/libdb.so.3
/usr/lib/libdb_cxx-4.so -> libdb_cxx-4.0.so
/usr/lib/libdb_cxx.so -> libdb_cxx-4.1.so
# ldd libsasldb.so
libdb-4.1.so => /usr/lib/libdb-4.1.so
The problem is I could not make OpenLDAP 2.1.13 build with libdb-4.1.so.
No matter how I try, it ALWAYS links with libdb-4.0.so annoyingly.
Why does cyrus-sasl (which *DOES NOT* require Berkeley DB 4.1 to operate) links
with libdb-4.1.so successfully, while OpenLDAP 2.1.13 (which *DOES NEED* 4.1 to
operate) do not?
I observed several program packages, including cyrus-sasl, PHP, etc. They DO
have special `configure' options like this:
# cd cyrus-sasl-2.1.12
# ./configure --help
--with-bdb-libdir=DIR Berkeley DB lib files are in DIR
--with-bdb-incdir=DIR Berkeley DB include files are in DIR
Why does OpenLDAP project doesn't have any, while it is STRONGLY dependent on
I hope I didn't miss anything.
I hope OpenLDAP team would help me and other SuSE users to get out of this