Openldap ./configure errors

This is a discussion on Openldap ./configure errors within the Linux Administration forums, part of the Linux Forums category; checking for Berkeley DB link (default)... no checking for Berkeley DB link (-ldb41)... no checking for Berkeley DB link (-ldb-...


Go Back   Usenet Forums > Linux Forums > Linux Administration

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 08-20-2003
Yossarian
 
Posts: n/a
Default Openldap ./configure errors

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 get the above errors when I try to ./configure openldap to work with
Berkely DB.

I have used other commands to set the environment correctly:

env CPPFLAGS=-I/usr/local/BerkeleyDB.4.1/include \

LDFLAGS=-L/usr/local/BerkeleyDB.4.1/lib \

../configure --enable-ldbm --prefix=/usr/local/openldap-2.1.22 \

--enable-monitor

Also I did a search on db.h/ndb.h and (libdb*.{a,so}), and I found many
versions of the same file such as 4.0, 4.1, etc as well as different date
stamps for files call db.h in various directories. Now how do I get all
those files to work coherently with Openldap and Berkeley DB 4.1? Thank you.

Yossarian


Reply With Quote
  #2 (permalink)  
Old 08-20-2003
Tim Teulings
 
Posts: n/a
Default Re: Openldap ./configure errors

Hallo!


> 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


Part of the result of a (failed) configure process should always be
a configure.log (or similar) that contains all lowelevel actions
the script did. Take a look at it which statement (likely a little
test compile/link) the configure executed and in which error message
this resulted. Try to do the same manually on the console.

This should show you the problem in more detail (perhaps wrong search
paths, etc..).

--
Gruß...
Tim.
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT +1. The time now is 12:26 PM.


Powered by vBulletin® Version 3.6.8
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0