You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "Wadsworth, Eric (Contractor)" <wa...@fhu.disa.mil> on 2003/11/17 15:15:51 UTC
Is BDB 4.1.25 okay?
I'm still trying to get my server going, but the build is choking on my BDB.
I installed 4.1.25 (the only one available anymore on
http://www.sleepycat.com/download/index.shtml) using the defaults, and did
this command:
./configure --with-berkeley-db=/usr/local/BerkeleyBD.4.1
Here's where the database was installed:
root-codebase$ls -la
total 12
drwxr-xr-x 6 root other 512 Nov 14 15:11 .
drwxr-xr-x 16 root sys 512 Nov 14 15:11 ..
drwxr-xr-x 2 root other 512 Nov 14 15:11 bin
drwxr-xr-x 10 root other 512 Nov 14 15:11 docs
drwxr-xr-x 2 root other 512 Nov 14 15:11 include
drwxr-xr-x 2 root other 512 Nov 14 15:11 lib
root-codebase$pwd
/usr/local/BerkeleyDB.4.1
Here's what ./configure said:
[...]
checking checking for Berkeley DB 4.1 in /usr/local/BerkeleyDB.4.1...
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.1...
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.1...
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.1...
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.1...
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 /usr/local/BerkeleyDB.4.1...
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
I don't know if this is pertinent, but in preparing to install, I didn't
realize that APR came with Apache (duh) so I installed it seperately. It's
still sitting there, and the ./configure script reports it finds APR 0.9.5
when it runs.
Any ideas what's going on here?
--- Eric
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Is BDB 4.1.25 okay?
Posted by Ben Collins-Sussman <su...@collab.net>.
On Mon, 2003-11-17 at 09:15, Wadsworth, Eric (Contractor) wrote:
> ./configure --with-berkeley-db=/usr/local/BerkeleyBD.4.1
>
Maybe because you mistyped the path to BDB there? :-)
Whatever the case, make sure that the BerkeleyDB libs are in your
LD_LIBRARY_PATH, or else the configure test will fail.
Actually, let me summarize the larger picture here. As of svn 0.33, our
BDB build strategy has changed:
* apr-util now looks for all versions of BDB, and chooses one.
* Subversion's configure simply asks the installed apr-util for BDB.
This prevents Subversion and Apache/apr-util from using two different
versions of BDB.
This means that the best way to do things is:
* make sure BDB 4.0 or 4.1 is installed at location $FOO
* make sure $FOO is in your $LD_LIBRARY_PATH
* unpack the httpd tarball, run
./configure --with-berkeley-db=$FOO --with-dbm=db4 (plus other args)
These two arguments get passed down to apr-util's configure -- it
tells apr-util where to find BDB, and specifically to only choose db4 if
multiple db versions are available.
* configure subversion with no mention of BDB stuff. It only needs to
find apr-util and "ask" for the BDB build info. (If apache is installed
in /usr/local/apache2/, this will happen automatically, else you need to
pass --with-apr=, --with-apr-util=)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Is BDB 4.1.25 okay?
Posted by Ben Collins-Sussman <su...@collab.net>.
On Mon, 2003-11-17 at 09:15, Wadsworth, Eric (Contractor) wrote:
> ./configure --with-berkeley-db=/usr/local/BerkeleyBD.4.1
>
Maybe because you mistyped the path to BDB there? :-)
Whatever the case, make sure that the BerkeleyDB libs are in your
LD_LIBRARY_PATH, or else the configure test will fail.
Actually, let me summarize the larger picture here. As of svn 0.33, our
BDB build strategy has changed:
* apr-util now looks for all versions of BDB, and chooses one.
* Subversion's configure simply asks the installed apr-util for BDB.
This prevents Subversion and Apache/apr-util from using two different
versions of BDB.
This means that the best way to do things is:
* make sure BDB 4.0 or 4.1 is installed at location $FOO
* make sure $FOO is in your $LD_LIBRARY_PATH
* unpack the httpd tarball, run
./configure --with-berkeley-db=$FOO --with-dbm=db4 (plus other args)
These two arguments get passed down to apr-util's configure -- it
tells apr-util where to find BDB, and specifically to only choose db4 if
multiple db versions are available.
* configure subversion with no mention of BDB stuff. It only needs to
find apr-util and "ask" for the BDB build info. (If apache is installed
in /usr/local/apache2/, this will happen automatically, else you need to
pass --with-apr=, --with-apr-util=)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org