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

Apache 2.2.14 keeps seeing a 2.0.x svn module

From: Jeremy Aston <jeremy.aston_at_realitylogic.com>
Date: Mon, 26 Oct 2009 14:32:22 +0000


I have been trying to upgrade my subversion to 1.6.6 and having some

Originally I was running Apache 2.2.8 and svn 1.4.6. I am on a VPS on a
Redhat 4.1.1-53 on a Intel E5320 (64 bit) platform.

I then download the source for svn 1.6.6 and dependencies and compiled
it. When I restarted Apache it failed with a signature exception on the
svn modules. The signature on the modules were for Apache 2.0 and not
2.2 which is weird given I was already running on 2.2.x. The server did
already have Apache 2 on it as the base install so I think somehow it is
finding the 2.0 Apache even though the last time I built Apache and svn
it worked fine.

I then thought I would rebuild Apache so I got 2.2.14 and built that
then rebuilt svn - same problem.

Since then I have tried LOADS of things. I have used --with-apr,
--with-apr-util and --with-apxs (in various combinations). This caused
a fail on libexpat not being found. I have removed the svn dependencies
and built from newly download apr/apr-util/expat. I have reloaded the
ld cache with library paths all over the place. I've done everything I
can think of to sort the problem but to no avail.

The only way I got subversion to compile against my fresh apr/apr-util
and expat was to compile apr-util with a --with-expat-builtin config option.

What do I need to do to force svn to compile against my Apache 2.2.14?

Many thanks in advance,



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-26 15:33:46 CET

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