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

Re: BDB mismatch problem



Howard Chu wrote:
See ITS#3809.

Wow. Thanks!

It worked fine with the following in my (tcsh) environment:

setenv CC gcc
setenv CFLAGS "-O -g"
setenv CPPFLAGS "-I/usr/local/include"
setenv LDFLAGS "-L/usr/local/lib"
setenv LD_LIBRARY_PATH "/usr/local/lib"
setenv ol_cv_db_db_4_dot_3 no

I understand Kurt's reasoning, but if BDB 4.2.52 is still preferred over 4.3 for OpenLDAP installs, I personally would side with Walter on redoing the way configure finds this particular library.

By strange coincidence, ITS#3909 might be the same issue, although it's not worded well enough to say.

Thanks again.

Jon Roberts
www.mentata.com

Jon Roberts wrote:
FC4
OpenLDAP 2.3.4
BDB 4.2.52 w/patches

This should be an easy issue, but I am getting stuck on configure. I installed BDB from source myself in /usr/local paths, so I have:

> ls -l /usr/local/lib
total 17888
-rw-r--r--  1 user user  6984362 Aug  1 10:13 libdb-4.2.a
-rw-rw-r--  1 user user      819 Aug  1 10:12 libdb-4.2.la
-rwxrwxr-x  1 user user  4275109 Aug  1 10:12 libdb-4.2.so
lrwxrwxrwx  1 root root       12 Aug  1 10:13 libdb-4.so -> libdb-4.2.so
-rw-r--r--  1 user user  6984362 Aug  1 10:13 libdb.a
lrwxrwxrwx  1 root root       12 Aug  1 10:13 libdb.so -> libdb-4.2.so

I know FC4 has BDB 4.3 installed in /usr/lib, but I thought this environment would override that:

setenv CC gcc
setenv CFLAGS "-O -g"
setenv CPPFLAGS "-I/usr/local/include"
setenv LDFLAGS "-L/usr/local/lib"
setenv LD_LIBRARY_PATH "/usr/local/lib"

However, on configure I'm getting:

...
checking for db.h... yes
checking for Berkeley DB link (default)... no
checking for Berkeley DB link (-ldb43)... no
checking for Berkeley DB link (-ldb-43)... no
checking for Berkeley DB link (-ldb-4.3)... yes
checking for Berkeley DB version match... Berkeley DB version mismatch
header: Sleepycat Software: Berkeley DB 4.2.52: (December 3, 2003)
library: Sleepycat Software: Berkeley DB 4.3.27: (April 25, 2005)
no
configure: error: Berkeley DB version mismatch


I could no doubt rename the db-4.3 library files, but I want the cleanest possible install procedure. Is there something I can change to keep configure from picking up the stock BDB where it lies?

Jon Roberts
www.mentata.com