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

RE: installing v2.03 with berkeleyDB, Linux


I had the same problem which was the reason for my original post.  I now
think I have found a solution.

1) Configure Berkeley DB using:
     > ../dist/configure --prefix=/usr/local
This installs the software into /usr/local instead of the default

2) Create a link from /usr/local/lib/libdb3.a to /usr/local/lib/libdb.a i.e.
     > ln -s libdb.a libdb3.a  (in /usr/local/lib)

3) Build OpenLDAP 2.0.3 in the usual way.

Looks like OpenLDAP's configure script will only pick up Berkeley DB if it
finds a libdb3.a library.


-----Original Message-----
From: owner-openldap-software@OpenLDAP.org
[mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of Daniel Tiefnig
Sent: Thursday, September 21, 2000 7:02 AM
To: OpenLDAP-Software
Subject: installing v2.03 with berkeleyDB, Linux


i installed berkeleyDB 3.1.17 too and then i launched configure with:

env CFLAGS="-D_REENTRANT" ./configure --prefix=/usr/local/openldap

and i've now a question concerning the output of configure:

--- snip ---
checking for NT Threads... checking for _beginthread... no
checking for pthread.h... yes
checking POSIX thread version... final
checking for LinuxThreads pthread.h... yes
checking for GNU Pth pthread.h... no
checking for sched.h... yes
checking for pthread_create in default libraries... no
checking for pthread link with -kthread... no
checking for pthread link with -pthread... yes
checking for sched_yield... yes
checking for pthread_yield... no
checking for pthread_kill... yes
checking for pthread_rwlock_destroy... yes
checking for pthread_detach with <pthread.h>... yes
checking for pthread_setconcurrency... yes
checking for pthread_getconcurrency... yes
checking for thr_setconcurrency... no
checking for thr_getconcurrency... no
checking for pthread_kill_other_threads_np... yes
checking for LinuxThreads implementation... yes
checking for LinuxThreads consistency... yes
checking if pthread_create() works... yes
checking if select yields when using pthreads... yes
checking for thread specific errno... yes
checking for thread specific h_errno... yes
checking for db.h... yes
checking for Berkeley DB link (default)... no
checking for Berkeley DB link (-ldb)... no
checking for Berkeley DB link (-ldb3)... no
checking for Berkeley DB link (-ldb2)... no
checking for Berkeley DB link (-ldb1)... no
checking for MDBM library... checking for mdbm_set_chain... no
checking for mdbm_set_chain in -lmdbm... no
checking for mdbm.h... no
checking for db... no
checking for GDBM library... checking for gdbm_open... no
checking for gdbm_open in -lgdbm... yes
checking for gdbm.h... yes
checking for db... yes
checking for openlog... yes
--- snip ---

configure is checking for db.h (a berkleyDB-headerfile AFAIK) and
finding it.
but then everything else seems to fail till the GNU DBM check. will ldap
the berkleyDB nevertheless, or will i have to give some more env-vars or
options? or do i have a general problem with my berkleyDB-installation?
I'm running redhat 6.1 and berkeleyDB is installed in /usr.

thanx for your patience
Daniel Tiefnig

Karlauergürtel 1
A-8020 GRAZ