Thany you very much. That did the trick. -David --On Thursday, February 22, 2001 4:39 PM -0500 "Ramineni, Kiran" <[EMAIL PROTECTED]> wrote: > > > rm config.cache > > /usr/lib/libdb-3.a -> /usr/local/BerkeleyDB.3.1/lib/libdb.a > > > -----Original Message----- > From: David R Bosso > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Sent: 2/22/01 12:34 PM > Subject: SASL & db help please? > > I'm trying the below instructions on redhat 6.2 system with no joy. > I've > got berkeley db 3.2.9 in /usr/local/BerkeleyDB.3.2/ > > /usr/local/BerkeleyDB.3.2/lib is in ld.so.conf and /sbin/ldconfig has > been > run. > > I used: > CPPFLAGS="-I/usr/local/BerkeleyDB.3.2/include" > LDFLAGS="-L/usr/local/BerkeleyDB.3.2/lib" > ./configure --disable-krb4 --enable-login --with-dblib=berkeley > > as per your instructions below, and configure can't find db.h. If I > symlink db.h to /usr/include/ configure finds it, but I get: > > checking for db.h... yes > checking for db_create in -ldb-3... no > checking for db_create in -ldb... no > checking for db_open in -ldb... no > checking DB library to use... no > configure: warning: Disabling SASL authentication database support > > ??? How the heck do you get SASL to use the new db? It'd be nice if it > > had a --with-dbdir= configure option like IMAP. > > Thanks for any help. > > -David > > > --On Wednesday, February 14, 2001 6:52 PM -0600 Paul Wiechman > <[EMAIL PROTECTED]> wrote: > >> >> As far as the BerkeleyDB's, it has been on this list before. When >> compiling SASL... >> >> CPPFLAGS="-I<path to Berkeley includes>" LDFLAGS="-L<path to Berkeley >> libs>" ./configure --<name your options> >> >> Also, make sure you add the lib directory of the new Berkeley install > to >> your ld.so.conf and run ldconfig. >
