[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: back-bdb & DB 4.1.24
Jehan,
All that you should really need are the CPPFLAGS, LDFLAGS vars.
Let's assume that BDB is installed in /usr/local/BerkeleyDB.4.1 (the
default). In fact, I would verify that it did compile and install
properly.
Try the following:
% CPPFLAGS=-I/usr/local/BerkeleyDB.4.1/include \
LDFLAGS=-L/usr/local/BerkeleyDB.4.1/lib \
./configure
Sasha
>-----Original Message-----
>From: owner-openldap-software@OpenLDAP.org
>[mailto:owner-openldap-software@OpenLDAP.org] On Behalf Of
>Jehan PROCACCIA
>Sent: Tuesday, November 12, 2002 7:10 AM
>To: OpenLDAP-software@OpenLDAP.org
>Subject: back-bdb & DB 4.1.24
>
>
>hello
>
>I want to compile openldap 2.1.8, and use BDB 4.1.24
>I did compile and Install BDB 4.1.24, but I dont know how to
>tell openldap configure script to link against my local
>version of BDB 4.1.24 and not the system one which is BDB 4.0.14 .
>
>I read in the lists people using --with-bdb-libdir
>--with-bdb-incdir others; --with-bdb-lib-dir
>--with-bdb-include-dir and also (CCPFLAGS=-I...
>LDFLAGS=-L...). What suprise me is that none of these options
>appears in a ./configure --help !? Are these OK ? is this
>documented somewhere ?
>
>Here's how I ran configure script, From config.status:
>
>echo "running ${CONFIG_SHELL-/bin/sh} ./configure
>--enable-debug --enable-crypt --enable-modules --enable-bdb
>--with-bdb-module=dynamic --enable-ldbm
>--with-ldbm-api=berkeley --with-ldbm-module=dynamic
>--enable-monitor --with-monitor-module=dynamic --enable-local
>--enable-cldap --disable-rlookups --with-tls --with-cyrus-sasl
>--enable-wrappers --enable-passwd --enable-shell
>--enable-cleartext --enable-spasswd
>--with-bdb-libdir=/usr/local/src/jehan/bdb/lib
>--with-bdb-incdir=/usr/local/src/jehan/bdb/include --no-create
>--no-recursion"
>
>Here's the result -> libdb4.0 :-(
>[root@corbeau /usr/local/src/openldap-2.1.8/servers/slapd]
>$ ldd ./slapd
> libdb-4.0.so => /lib/libdb-4.0.so (0x40021000)
> libssl.so.2 => /lib/libssl.so.2 (0x400ca000)
> libcrypto.so.2 => /lib/libcrypto.so.2 (0x400fa000)
> libcrypt.so.1 => /lib/libcrypt.so.1 (0x401ce000)
> libresolv.so.2 => /lib/libresolv.so.2 (0x401fb000)
> libnsl.so.1 => /lib/libnsl.so.1 (0x4020d000)
> libdl.so.2 => /lib/libdl.so.2 (0x40222000)
> libpthread.so.0 => /lib/i686/libpthread.so.0 (0x40226000)
> libc.so.6 => /lib/i686/libc.so.6 (0x42000000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
>
>Any help ?
>
>thanks
>
>--
>Jehan Procaccia
>Institut National des Telecommunications| Email:
>Jehan.Procaccia@int-evry.fr
>MCI, Moyens Communs Informatiques | Tel : +33 (0) 160764436
>9 rue Charles Fourier 91011 Evry France | Fax : +33 (0) 160764321
>