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

Re: Problem Compiling Subversion with BerkeleyDB

From: Farid Izem <farid.izem_at_gmail.com>
Date: 2006-06-15 23:39:49 CEST

Hi all,

Well, Compiling subversion with berkeleyDB on Redhat WS 3 and Solaris 10 is
a problem.

When compiling on Redhat WS 4 and Fedora 3 and 4, it compiles perfectly.
i have check using ldd to see which library the mod_svn_dav.so or
mod_dav_svn.so (don't rememeber, this is night in France) what link to.

I'm still loooking at a workaround but in my opinion, the problem is still
the same
With Apache and BerkeleyDB support.

This is the way i compile subversion on Fedora Core 3 :

Compile Apache including BerkeleyDB :
 ./configure --prefix=PREFIXyouWANT
make install
Check $PREFIX/bin/apu-1-config --db-version ==> should return 4

Compiling Subversion : Apache Portable Runtime of Subversion and httpd soulh
be the Same. Please use Apache Portable from httpd.

./configure --prefix=PREFIXyouWANT --with-apxs=PATHtoAPX
--with-apr=PATHtoAPR --with-apr-util=PATHtoAPUCONFIG
make install

should be link to berkelyDB as apr-1-config and apu-1-config are link to
from apache compilation step.

But, now, i facing the problem of compiling Apache on Solaris and WS3 using
It's the same problem with subversion. If we solve it, we will be able to
compile subversion
Using BerkeleyDB.

Kind Regards,


On 6/14/06, David Mahakian <tmoli42@gmx.net> wrote:
> C. Michael Pilato wrote:
> > [Sending to the correct list. Note that I am not subscribed to users@.]
> >
> > Farid Izem wrote:
> >> Hi all,
> >>
> >> I'm tring to compile SubVersion 1.1.4 and 1.3.2 on RedHat WS 3.
> >> I'm still facing a problem during the configure step.
> >>
> >> ./configure --prefix=/home/user01/base_subversion/subversion-1.1.4_depl
> >> --with-berkeleyd-db=/home/user01/base_berkeley/db-4.2.52depl
> >> --with-apxs=/home/user01/base_apache/http-2.2.2_depl/bin/apxs
> >>
> >> I'm still having the problem BerkeleyDb not found :
> >> configure: error: Berkeley DB not found.
> >> configure failed for apr-util.
> >
> > Chances are good that the linker isn't able to hook up Subversion with
> BDB.
> > As you are building all this stuff in a home directory, I'm going to
> > presume that /etc/ld.so.conf hasn't been updated with a reference to
> your
> > BDB libdir and /sbin/ldconfig rerun to make that change take
> effect. So, as
> > a fallback, does your LD_CONFIG variable contain a reference to the BDB
> > libdir (which I'm guessing is "/home/user01/base_berkeley/db-4.2.52depl
> /lib")?
> >
> I had a similar problem on my system (Ubuntu 5.10) and just figured it
> out yesterday. The problem with mine was that I compiled and installed
> 4.3.29, but Ubuntu ships with BDB 4.3.28. The header file check in
> configure for apr-util passes, but the library test fails. Ie (excerpted
> lines only):
> configure:18564: checking db.h presence
> configure:18600: result: yes
> configure:18635: checking for db.h
> configure:18642: result: yes
> configure:18658: checking for -ldb-4.3
> configure:18754: result: no
> Check your config.log in apr util for similar messages.
> By taking a closer look I realized that what happened is that the Ubuntu
> default bdb libraries in /usr/lib were being found first, so the library
> version found did not match the header. So then I instead used that
> version by --with-berkeley-db=/usr. That fixed it.
> If RedHat also ships with a version of BDB, you may have the same issue
> and want to try similar. Make sure you install the berkeley db
> development rpm (if there is one, there was a separate package in Ubuntu
> for it), then try something similar to what I have done.
> When I searched online with similar problems, I think they all had the
> same problem as me. None of them had the problem resolved; the only
> advice they were given was to not compile with it.
> - David Mahakian
Received on Thu Jun 15 23:41:48 2006

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.