[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: ./configure refuses to see BerkeleyDB.4.2

From: <santanu.misra_at_reuters.com>
Date: 2004-07-23 11:54:32 CEST

Hello,

depending on your OS you need to add the lib for Berkeley DB in LD_LIBRARY_PATH
or edit /etc/ld.so.conf and run ldconfig after that.

hope this helps,
Santanu

                                                                                                                                       
                      Douglass Turner
                      <turner@mmedia.is To: users@subversion.tigris.org
> cc: Douglass Turner <turner@mmedia.is>
                                               Subject: ./configure refuses to see BerkeleyDB.4.2
                      23/07/2004 11:41
                                               Header: Internal Use Only
                                                                                                                                       
                                                                                                                                       
                                                                                                                                       

Hi,

Could someone please tell me how to convince ./configure that I do indeed
have BerkeleyDB.4.2 installed.

Here is the relevent info.

Berkeley DB:

cd /usr/local/BerkeleyDB.4.2

<122>[BerkeleyDB.4.2]% ls
bin/ docs/ include/ lib/

<123>[BerkeleyDB.4.2]% ls include/
db.h db_cxx.h

<124>[BerkeleyDB.4.2]% ls lib/
libdb-4.2.a libdb-4.2.la libdb-4.2.so* libdb-4.so@ libdb.a libdb.so@

Subversion:

The echo of ./configure:
./configure --with-berkeley-db=/usr/local/BerkeleyDB.4.2
...
checking checking for Berkeley DB 4.1 in /usr/local/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 /usr/local/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 /usr/local/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 /usr/local/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 /usr/local/BerkeleyDB.4.2...
checking db1/db.h usability... yes
checking db1/db.h presence... yes
checking for db1/db.h... yes
checking for dbopen in -ldb1... yes
  setting APRUTIL_INCLUDES to "-I/usr/local/BerkeleyDB.4.2/include"
  setting APRUTIL_LDFLAGS to "-L/usr/local/BerkeleyDB.4.2/lib"
checking for Berkeley DB... found db1
checking for default DBM... sdbm (default)
  setting APRUTIL_EXPORT_LIBS to "-ldb1"
  setting APRUTIL_LIBS to "-ldb1"
...

configure: WARNING: we have configured for a client-only build

The Subversion filesystem library, part of the server, requires
Berkeley DB version 4.0.14 or newer, which you don't seem to have
installed and linked to APR-UTIL. We have created makefiles which
will build the Subversion client code only, and skip the server. You
can find latest version of Berkeley DB at http://www.sleepycat.com/.
You can find the latest version of Berkeley DB here:
  http://www.sleepycat.com/download/index.shtml

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

-----------------------------------------------------------------
        Visit our Internet site at http://www.reuters.com

Get closer to the financial markets with Reuters Messaging - for more
information and to register, visit http://www.reuters.com/messaging

Any views expressed in this message are those of the individual
sender, except where the sender specifically states them to be
the views of Reuters Ltd.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 23 11:56:04 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.