You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Tom Brown <br...@esteem.com> on 2005/03/04 17:49:53 UTC

problems installing subversion

I am having problems installing subversion 1.1.3 onto a machine running RedHat 
7.1. I installed the Berkeley DB version 4.2.52 from source. Then I installed 
Apache 2.0.53 from source. Then I tried to configure subversion using:

./configure --with-apr=/usr/local/apache2 --with-apr-util=/usr/local/apache2

but got the following message:

You don't seem to have Berkeley DB version 4.0.14 or newer
installed and linked to APR-UTIL.  We have created Makefiles which
will build without the Berkeley DB back-end; your repositories will
use FSFS as the default back-end. You can find the latest version of
Berkeley DB here:
  http://www.sleepycat.com/download/index.shtml

So, I found a patch in FAQ for the Apache apr-util/configure script and 
applied that and tried to configure Apache using:

./configure --enable-dav --enable-so \ 
  --with-berkeley-db=/usr/local/BerkeleyDB.4.2 --with-dbm=db42

but configure failed with the following messages:

checking checking for Berkeley DB 4.2 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.2... 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
configure: error: Berkeley db4 not found
configure failed for srclib/apr-util

What am I doing wrong?

Thanks,
Tom

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

Re: problems installing subversion

Posted by David Ripton <dr...@ripton.net>.
On 2005.03.04 09:49:53 +0000, Tom Brown wrote:
> I am having problems installing subversion 1.1.3 onto a machine running RedHat 
> 7.1. I installed the Berkeley DB version 4.2.52 from source. Then I installed 
> Apache 2.0.53 from source. Then I tried to configure subversion using:
> 
> ./configure --with-apr=/usr/local/apache2 --with-apr-util=/usr/local/apache2
> 
> but got the following message:
> 
> You don't seem to have Berkeley DB version 4.0.14 or newer
> installed and linked to APR-UTIL.  We have created Makefiles which
> will build without the Berkeley DB back-end; your repositories will
> use FSFS as the default back-end. You can find the latest version of
> Berkeley DB here:
>   http://www.sleepycat.com/download/index.shtml
> 
> So, I found a patch in FAQ for the Apache apr-util/configure script and 
> applied that and tried to configure Apache using:
> 
> ./configure --enable-dav --enable-so \ 
>   --with-berkeley-db=/usr/local/BerkeleyDB.4.2 --with-dbm=db42
> 
> but configure failed with the following messages:
> 
> configure: error: Berkeley db4 not found
> configure failed for srclib/apr-util
> 
> What am I doing wrong?

Using BDB.  Use FSFS instead.  :->

I haven't built SVN on RH 7.1.

When this happened to me on another system (SVN 1.0.x on Gentoo), it was
because there were two versions of BDB (4.1.x installed by Gentoo, 4.2.x
installed by me) on the box, and the configure script was taking the one
that came first in some library path instead of the one I explicitly
told it to use.

(I think there's probably a bug in SVN's or apr's usage of
automake/autoconf, but I haven't learned enough auto* to prove that, let
alone fix the alleged bug.)

Use FSFS instead, and be happy.

If you can't do that, eradicate all but one version of BDB from the
system, and it'll work.

If you can't do that, you'll need to mess with various library load
paths (/etc/ld.so.conf, LD_LIBRARY_PATH, and similar evil) until BDB
version you want comes first.  

That last option is tricky, fragile, and not very recommended.  In
theory you could create a brittle SVN install where if a user has
LD_LIBRARY_PATH set right, SVN works, and if he has it set wrong, SVN
tries to use the wrong BDB version and possibly corrupts its repository.

-- 
David Ripton    dripton@ripton.net

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