On May 16, 2006, at 23:39, Jerry Zhao wrote:
> I am having problems running configure for subversion 1.3.1 with
> httpd-2.0.58 installed:
>
> ./configure --prefix=/home/svn-1.3.1 --with-ssl --with-apr=/home/
> httpd2 --with-apr-util=/home/httpd2 --with-apxs=/home/httpd2/sbin/
> apxs --disable-nls
>
> ...
> configure: Apache Portable Runtime (APR) library configuration
> checking for APR... yes
> checking APR version... 0.9.12
> wanted regex is 0\.9\.[5-9] or 1\.
> configure: error: invalid apr version found
Oop! Looks like someone never expected there to be a version of APR
0.9 greater than 0.9.9. Looks like this bug was already fixed in
Subversion trunk on March 26, 2006, in r19039:
http://svn.collab.net/viewvc/svn?view=rev&revision=19039
and improved/corrected in trunk r19057:
http://svn.collab.net/viewvc/svn?view=rev&revision=19057
and merged to the 1.3.x branch on April 2 in r19125:
http://svn.collab.net/viewvc/svn?view=rev&revision=19125
So it'll be in Subversion 1.3.2.
> So I modified the configure script to recognize the new apr
> version, but since httpd 2.0.58 no longer linked to bdb, configure
> still failed:
>
> ...
> configure: WARNING: we have configured without BDB filesystem support
>
>
> 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:
>
> Are these bugs or am I missing something? Any feedback is appreciated!
Is there a particular reason why you want BerkeleyDB? I recommend
building Subversion without it. There's a configure switch for that.
Or it sounds like the above is just a warning (not an error) which
you can just ignore.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 17 15:53:55 2006