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

Re: unable to build svn server: aprutils/bdb issues

From: Simon Kitching <simon_at_ecnetwork.co.nz>
Date: 2004-02-11 05:47:29 CET

Hi Ben,

Thanks for the info.

On Wed, 2004-02-11 at 06:30, Ben Collins-Sussman wrote:
> On Tue, 2004-02-10 at 09:11, Simon Kitching wrote:
> > Does anyone have any ideas what I am doing wrong? It sure looks to me
> > like apr-util doesn't yet support berkeley db newer than 4.1, but your
> > install docs recommend 4.2.51, so it must be possible...
> Yes, it's possible, but the latest released apr-util can't detect 4.2
> yet. Only the CVS HEAD of apr-util has that code at the moment.
> The formula is:
> * install DB4.2 somewhere on your system, like in
> /usr/local/BerkeleyDB.4.2
> * put /usr/local/BerkeleyDB.4.2/lib into /etc/ld.so.conf and run
> 'ldconfig'

> * tell apr-util (either directly, or through apache's configure) to use
> --with-berkeley-db=/usr/local/BerkeleyDB.4.2.

I tried downloading the latest apr-util snapshot. Of course it comes
without a configure file, unlike the apr-util subdir in httpd-2.0.48

I tried running autoconf but when the generated configure script is run,
it reports a syntax error. I've downloaded and compiled the latest
autoconf, and get the same result. &$&^%$@#!

Well, maybe I'll try again when a newer apache release is out with the
latest aprutil inside (including prebuilt configure file).

In the meantime I've downloaded BerkeleyDB 4.1, and built against that.
And it Just Works. yay. I can live without auto-log-cleaning for a

Oddly enough, ldd against the libaprutil-0.so file doesn't report any
BerkeleyDB libs dependencies, but subversion compiles the server stuff



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 11 05:48:52 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.