I've found the problem and it's a weird one to be certain (at least I think
OK, first I had apache installed (version 2.2) and I knew that apr-conf and
apu-conf exsisted, however they were entirely the wrong versions(kept coming
up at 0.9.7, when they should be 1.2.7). This is because the old apr-config
was in fact the dependancy version built from subversion, apr-1-config was
the apache version (same with apu). Ok so simple solution there, rename the
old apr-config to something else (I added a .old) and virtual link the other
one to that location. I did this for both apr and apu - config files which
fixed that problem.
Then I noticed that even thou I had built neon on my own (just like I built
the apr stuff) it was building it when it ran the subversion install, and
not with the flags I wanted it to build with. Ok so the problem here is
that the dependancy packages unpack to the subversion source directory,
which means when you do ./configure it finds them and builds them even if
you don't want it to. So, rename the folders to something it won't look in.
Then build the dependancies (in this case I only needed neon as apr was
provided by apache) and tell it to use them in the ./configure. Note it
will build apr and apr-util (just like neon) even if you have apache
installed so long as they are in the source directory so make sure you
After all this I can finally do make && make swig-py. Then do make install
&& make install-swig-py. Everything appears to be working and interacting
with the correct versions of the other software on the system.
So long and short, pay attention to what it's doing with your dependancy
files and make sure it's doing what you think it's supposed to be doing
because it usually isn't.
Hope that helps anybody else that is having weird problems like the afore
mentioned one I had.
From: Russ [mailto:firstname.lastname@example.org]
Sent: Tuesday, October 31, 2006 10:44 PM
To: gmcgrath@Princeton.EDU; email@example.com
Subject: Re: undefined symbol: svn_swig_get_application_pool
The latest version of svn seems to be a pain to build on the RedHat based
systems. I see you have neon configured properly with static and shared
libs. This was my problem when I tried compiling it. I didn't have to use
disable-neon-version-check' '--disable-mod-activation' when compiling
though.. Are you maybe using an incompatible version of neon? What version
of pyhon is it linking against? I don't think svn will work with 2.5, and I
had several versions installed on mine and had to specify the python flags.
Basically check the versions you're using and make sure that they're
supported. I've never seen your error though.
Sent wirelessly via BlackBerry from T-Mobile.
From: "Garrett McGrath" <gmcgrath@Princeton.EDU>
Date: Tue, 31 Oct 2006 12:24:42
Subject: undefined symbol: svn_swig_get_application_pool
This issue is starting to drive me a bit batty. So i've built svn with the
following config commands:
'./configure' '--prefix=/usr/local' '--with-ssl'
I've also run make swig-py and make install-swig-py
I've also built neon from the dependancy set for svn 1.4 using:
./configure --prefix=/usr/local/ --enable-shared --enable-static
--with-ssl=openssl --with-libs=/usr/local --enable-tests-install
ok so this appeared to get everything working. I could run svn to check
things out on http, https, svn, file, etc.
Unfortunatly when you go into python and enter 'import svn.repos' I get the
following error (on an asside i get no errors from import svn):
>>> import svn.repos
Traceback (most recent call last):
File "<stdin>", line 1, in ?
File "/usr/local/lib/svn-python/svn/repos.py", line 19, in ?
from libsvn.repos import *
File "/usr/local/lib/svn-python/libsvn/repos.py", line 5, in ?
ImportError: /usr/local/lib/svn-python/libsvn/_repos.so: undefined symbol:
I've tried everything I can think of including symbolic links for the svn
and libsvn folder in the site-packages area to no avail but really need to
get this fixed so I can get a web respository browser up and running (thru
the trac project manager system by edgewall). I've setup this system on
another system with no issues so I'm not sure what's going on here. The
server is running centos 4.3 (we've done a yum upgrade so it may be 4.4 now,
not sure thou).
Any help for this issue would be greatly appreciated.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Nov 1 16:07:01 2006