I installed Berkeley 4.2, the latest version, but configure seems to want 4.1 or older. Do I have to install 4.1 (or older) instead?
/apps/BerkeleyDB.4.2> ls -l lib
total 4027
-rw-r--r-- 1 smcclena 1442316 Jan 8 16:18 libdb-4.2.a
-rw-rw-r-- 1 smcclena 797 Jan 8 16:18 libdb-4.2.la
-rwxrwxr-x 1 smcclena 1190036 Jan 8 16:18 libdb-4.2.so
lrwxrwxrwx 1 smcclena 12 Jan 8 16:36 libdb-4.so -> libdb-4.2.so
-rw-r--r-- 1 smcclena 1442316 Jan 8 16:18 libdb.a
lrwxrwxrwx 1 smcclena 12 Jan 8 16:36 libdb.so -> libdb-4.2.so
/apps/BerkeleyDB.4.2> ls -l include
total 112
-r--r--r-- 1 smcclena 80450 Jan 8 16:07 db.h
-r--r--r-- 1 smcclena 33181 Jan 8 16:07 db_cxx.h
From db.h:
/*
* Berkeley DB version information.
*/
#define DB_VERSION_MAJOR 4
#define DB_VERSION_MINOR 2
#define DB_VERSION_PATCH 52
#define DB_VERSION_STRING "Sleepycat Software: Berkeley DB 4.2.52: (December 3, 2003)"
...
checking checking for Berkeley DB 4.1 in /apps/BerkeleyDB.4.2...
checking db4/db.h usability... no
checking db4/db.h presence... no
checking for db4/db.h... no
checking db.h usability... yes
checking db.h presence... yes
checking for db.h... yes
checking for db-4.1... no
checking db4/db.h usability... no
checking db4/db.h presence... no
checking for db4/db.h... no
checking db.h usability... yes
checking db.h presence... yes
checking for db.h... yes
checking for db4... no
checking db4/db.h usability... no
checking db4/db.h presence... no
checking for db4/db.h... no
checking db.h usability... yes
checking db.h presence... yes
checking for db.h... yes
checking for db... no
checking checking for Berkeley DB 4.0 in /apps/BerkeleyDB.4.2...
checking db4/db.h usability... no
checking db4/db.h presence... no
checking for db4/db.h... no
checking db.h usability... yes
checking db.h presence... yes
checking for db.h... yes
checking for db-4.0... no
checking db4/db.h usability... no
checking db4/db.h presence... no
checking for db4/db.h... no
checking db.h usability... yes
checking db.h presence... yes
checking for db.h... yes
checking for db4... no
checking db4/db.h usability... no
checking db4/db.h presence... no
checking for db4/db.h... no
checking db.h usability... yes
checking db.h presence... yes
checking for db.h... yes
checking for db... no
checking checking for Berkeley DB 3 in /apps/BerkeleyDB.4.2...
checking db3/db.h usability... no
checking db3/db.h presence... no
checking for db3/db.h... no
checking db.h usability... yes
checking db.h presence... yes
checking for db.h... yes
checking for db3... no
checking db3/db.h usability... no
checking db3/db.h presence... no
checking for db3/db.h... no
checking db.h usability... yes
checking db.h presence... yes
checking for db.h... yes
checking for db... no
checking checking for Berkeley DB 2 in /apps/BerkeleyDB.4.2...
checking db2/db.h usability... no
checking db2/db.h presence... no
checking for db2/db.h... no
checking db.h usability... yes
checking db.h presence... yes
checking for db.h... yes
checking for db_open in -ldb2... no
checking db2/db.h usability... no
checking db2/db.h presence... no
checking for db2/db.h... no
checking db.h usability... yes
checking db.h presence... yes
checking for db.h... yes
checking for db_open in -ldb... no
checking checking for Berkeley DB 1.0.0 in /apps/BerkeleyDB.4.2...
checking db1/db.h usability... no
checking db1/db.h presence... no
checking for db1/db.h... no
checking db.h usability... yes
checking db.h presence... yes
checking for db.h... yes
checking for dbopen in -ldb1... no
checking checking for Berkeley DB 1 in /apps/BerkeleyDB.4.2...
checking db_185.h usability... no
checking db_185.h presence... no
checking for db_185.h... no
checking for Berkeley DB... not found
configure: error: Berkeley DB not found.
configure failed for apr-util
--------------------------
NOTE: This message and any included attachments are from HealthCom Partners, LLC and are intended only for the addressee(s). The information contained herein may include trade secrets or privileged or otherwise confidential information. Unauthorized review, forwarding, printing, copying, distributing, or using such information is strictly prohibited and may be unlawful. If you received this message in error, or have reason to believe you are not authorized to receive it, please promptly delete this message and notify the sender by e-mail.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 9 00:00:43 2004