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

Re: Installing/Building

From: WC -Sx- Jones <lists_at_insecurity.org>
Date: 2003-05-18 06:47:21 CEST

On Saturday, May 17, 2003, at 07:27 PM, Michael Suess wrote:

> Am Sam, 2003-05-17 um 13.36 schrieb WC Jones:
> [snip]
>> Speaking of script maintenance; the ./configure --help states that
>> XX.XX version of DB or newer is required to build -- but it never
>> states what version - it just says xx.xx
>> I have Db4.1.x and even though the script 'sees' the Berkley installed
>> directory, it still says is cannot use it...
>> Any ideas???
> Subversion officially recommends the use of Berkeley DB 4.0.14, however
> a couple of people (including myself) are successfully using a db
> 4.1.xx
> (xx=25 in my case) - with no problems I should add. All I had to do to
> get it to work, was add the option
> --with-berkeley-db=/path/to/BerkeleyDB.4.1
> to configure (and the corresponding lines to the apache config as well,
> if you are planning on using dav). I guess you already did that, as you
> seem to have found the --help option.
> If that did not work for you, you might have to tell us a little more
> about your environment, at least what version of Subversion you are
> using on what operating system, and how exactly the configure script
> errors out...

Hmmm, maybe DAV is the issue.

Are you using Apache 1.3.27 or 2.x ???

I am using Solaris 9 UltraSparc - Apache 2.0.45 with Dav/2, mod_ssl,
... and Db 4.1.25

Let me attack it by turning off DAV/2, et al, and try it with a plain
ol' Apache 2.0.45 =)

Thx =)
  ('> iudicium ferat
  //\ Have Computer -
  v_/_ Will Hack...

               \|/ ____ \|/
               "@'/ .. \`@"
               /_| \__/ |_\

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun May 18 06:48:01 2003

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.