Jason Morgan wrote:
> Hi,
>
> Now 1.5 is released, I'd like to move my repository from Win32/Apache to
> Linux/Apache.
>
> So, I'm trying to build subversion1.5.0 under ubuntu server (Gutsy), but
> have run into problems at the first hurdle.
>
> On ./configure I get a message about
>
> root_at_digger:/usr/src/subversion-1.5.0# ./configure
> ...
> ...
> ...
> 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.oracle.com/technology/software/products/berkeley-db/index.html
>
>
> or
>
> root_at_digger:/usr/src/subversion-1.5.0# ./configure --with-berkeley-db=/usr
> ...
> ...
> ...
> configure: WARNING: APR-UTIL may or may not be using the specified
> Berkeley DB at `/usr'. Using the Berkeley DB
> supplied by APR-UTIL.
> checking for availability of Berkeley DB... no
> configure: error: Berkeley DB 4.0.14 wasn't found.
>
> Complete configure logs here.
> http://rafb.net/p/bQYBRN13.html
> http://rafb.net/p/tHkV7E96.html
>
>
> db4.4 and db4.4-dev are both installed, I have also tried with BerkeleyDB4.4
> source build installed and pointed to its lib install folder with the same
> results.
>
> Googling this problem results in many instances of it in the past, so I
> don't think its specific to 1.5, though I can't find a resolution.
> Methinks the problem is a mistake in the configure script that makes
> assumptions about where certain thing exist. I've no idea what apt-util is,
> but I suspect that it's party to the cause.
In order to use the Berkeley DB backend, apr-util has to be configured
with it. Subversion uses the output of apu-config to determine if that
is the case, and configures itself appropriately. Unfortunately,
apu-config appears to be broken on Ubuntu systems, see
https://bugs.launchpad.net/ubuntu/+source/apr-util/+bug/96980
The bug is over a year old, maybe making some noise about it will help
solve the problem. In the short term, though, you can either live
without BDB support, which isn't crucial, or download and compile a
custom apr-util which is configured for Berkeley DB.
-Hyrum
Received on 2008-06-27 17:37:19 CEST