Next message: Carson Gaspar: "Re: problem cyrus-sasl with berkeley db 3.3 and db4.2.52"
On Wed, Jun 09, 2004 at 10:23:32AM +0200, amendola maurizio wrote:
> checking for db.h... (cached) yes
> checking for db_create in -ldb-4.2... (cached) no
> checking for db_create in -ldb4.2... (cached) no
> checking for db_create in -ldb42... (cached) no
> checking for db_create in -ldb-4.1... (cached) no
> checking for db_create in -ldb4.1... (cached) no
> checking for db_create in -ldb41... (cached) no
> checking for db_create in -ldb-4.0... (cached) no
> checking for db_create in -ldb4.0... (cached) no
> checking for db_create in -ldb-4... (cached) no
> checking for db_create in -ldb40... (cached) no
> checking for db_create in -ldb4... (cached) no
> checking for db_create in -ldb-3.3... (cached) yes
> checking DB library to use... berkeley
I ran into this myself yesterday on my Debian unstable system.
The problem is that configure is checking for the name
"db_create" in the Berkeley DB library files that it finds.
At least with the very latest Berkeley DB, this symbol is now
called "db_create_4002" and there are macros in <db.h> which
define db_create to be db_create_4002.
The aclocal.m4 file needs to be updated so that the test
program includes <db.h> or that it checks for both possible
symbol names.
--
Caleb Epstein | bklyn . org | You single-handedly fought your way into this
cae at | Brooklyn Dust | hopeless mess.
bklyn dot org | Bunny Mfg. |
