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

Re: problems building SVN (and http2.0)

From: Seth Landsman <seth_at_boondock.cs.brandeis.edu>
Date: 2002-12-16 22:04:57 CET

> > I'm trying to get the subversion server built on my linux
> >server. I'm trying to follow the INSTALL document directions as closely
> >as possible, but I'm hitting a brick wall in trying to get http2.0
> >compiled. I know that is not strictly part of subversion, but I can
> >build apache2 if I let it pick its own db implementation.
> >
> > Here are the details.
> >
> >The machine is running debian testing, up to date as of a couple of days
> >ago. I've installed the libdb4.0-dev package (and I've also tried
> >building my own and installing it in /usr/local/Berkeley4.0, with the
> >same results).
> >
> >The configure line is:
> >
> >./configure --enable-dav --enable-so --prefix=/usr/local/apache2
> >--with-dbm=db4
> >
> >
>
> you might need a --with-berkeley-db= line in there to tell it where your
> berkeley db headers and libs are, if they aren't in an obvious place.

        I've tried that.

        When I had my own copy of BerkeleyDB 4 installed in
/usr/local/Berkeley4.0, I give it an appropriate --with-berkeley-db
line, and got the same set of errors.

        Currently, I'm using the debian package, so everything is
installed with the /usr prefix.

        According to the config line, it looks like it is finding the
library and header files, but the function it is looking for
(db_create()) isn't there.

-Seth

>
> -garrett
>
>
>

-- 
it is by will alone I set my mind in motion
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Dec 16 22:05:41 2002

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.