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

RE: Apache 2.2.14 keeps seeing a 2.0.x svn module

From: Tena Sakai <tsakai_at_gallo.ucsf.edu>
Date: Mon, 26 Oct 2009 11:04:31 -0700

Hi Jez,

I am not an expert at subversion, but your case
interests me because I had similar symptom as
yours a week or so ago.

I had apache server 2.0 running and what I wound
up doing was to download the latest httpd and
compiled it, stopped the 2.0 apache, and started
2.2 apache. Then recompiled the subversion from
./configure which went smoothly and subversion
started working. Since the binding to apr is
already done, I stopped the apache server and
started the 2.0 apache and all is well. (Of
course, I had to do this all at wee hour of the

I emphasize that your situation is probably
different from mine in lots of ways, but the
symptom sounds suspiciously similar. So, if
I were you, I would try the following experiments:

1) Hide all apache tree. Maybe chmod 000 the-tree.
   or rename it. Stop apache and recompile
   apache under a virgin directory. Test the
   apache only.
2) If the step 1 above goes well, I would do
   ./configure and the rest of it in subversion
   source directory and see what would happen.

Don't just do it. Give enough thoughts in advance
so that you can recover to the point before the
experiment if the result proves undesirable.

Hope this helps.


Tena Sakai

-----Original Message-----
From: Jeremy Aston [mailto:jeremy.aston_at_realitylogic.com]
Sent: Mon 10/26/2009 7:32 AM
To: users_at_subversion.tigris.org
Subject: Apache 2.2.14 keeps seeing a 2.0.x svn module

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].


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-26 19:06:55 CET

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