[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: BerkeleyDB version incompatible
David Hofer wrote:
checking if select yields when using pthreads... yes
checking for thread specific errno... yes
checking for thread specific h_errno... yes
checking for ctime_r... yes
checking for gethostbyname_r... yes
checking for gethostbyaddr_r... yes
checking number of arguments of ctime_r... 2
checking number of arguments of gethostbyname_r... 6
checking number of arguments of gethostbyaddr_r... 8
checking for db.h... yes
checking for Berkeley DB link (default)... no
checking for Berkeley DB link (-ldb41)... no
checking for Berkeley DB link (-ldb-41)... no
checking for Berkeley DB link (-ldb-4.1)... yes
checking for Berkeley DB thread support... no
checking Berkeley DB version for BDB backend... no
configure: error: BDB: BerkeleyDB version incompatible
I have been pulling my hair out over this. Anyway I am using Openldap
2.1.22 and Berkeley DB 4.1.25, and I have used the ln -s command to link
BerkeleyDB with BerkeleyDB4.1, but I still get the same config error
with Openldap.Please tell me how I am in error for the good of my soul.
Sincerely,
David Hofer
David,
I had a similar problem building openLDAP on RH9, the ./configure script
(if your building openLDAP from tarball) will look in /usr/lib for the
Berkley DB files, I obviously had a lower version of Berkley db as RH9
uses 4.0.
Looking at the ones I moved from my /usr/local/Berleydb41/lib directory
files are libdb-4.1.a libdb-4.1.la libdb-4.1.so The symlinks are
libdb-4.so -> libdb-4.1.so and libdb.a -> libdb-4.1.a again in /usr/local
Once this was done ./configured worked fine
Hope this helps
Greg
--
Support Engineer
Tel: +44 1444
Fax: +44 1444
Disclaimer
Please note: This email is confidential and may also be privileged.
Please notify us immediately, if you are not the intended recipient.
You should not copy it, forward it or use it for any purpose or disclose
its contents to any person.
In sending this email, the sender is not acting as an agent,
representative or in any other capacity for or on behalf of TSS.
We cannot accept liability for any loss or damage caused by software
viruses.