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

Re: Where oh where has my Berkeley DB gone? (Issue 544)

From: Greg Stein <gstein_at_lyra.org>
Date: 2001-11-01 09:58:58 CET

On Thu, Nov 01, 2001 at 04:51:20AM +0000, Philip Martin wrote:
> "B. W. Fitzpatrick" <fitz@red-bean.com> writes:
>
> > Any configure hackers out there want to take a crack at this? I've

Watch out if you use the --config-cache switch. We cache where we find (or
don't find) DB. So if you have a cache that says it doesn't exist somewhere,
then you install it, then rerun config -- it won't find it. Gotta wipe the
cache, or just not use it.

>...
> > Scenario:
> >
> > - Download Berkeley DB 3.3.11, untar and move it to subversion/db
> > - cd db/build_unix
> > - run ../dist/configure && make && make install
> > - cd back into the subversion build root

If you're going to install it separately, then I don't think you should
locate the thing in the db/ subdirectory.

>...
> > configure then gives me this line:
> >
> > checking for Berkeley DB in /usr/local/BerkeleyDB.3.3... no
>
> So are there errors in config.log relating to the tests for Berkeley?
>
> One guess: do you need to add /usr/local/BerkeleyDB.3.3/lib to your
> library search path (LD_LIBRARY_PATH or /etc/ld.so.conf)?

This latter issue is what got me when I set up my new box at work. I had
forgotten to add it to ld.so.conf and run ldconfig first. When configure
tried to link against the library to check its version... blam! No workie.
So configure assumed the library wasn't there after all.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:46 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.