A little off topic but I think the answer will resolve the problem
I've been having.

I've discovered that subversion is using the system-installed libapr
and libaprutil libraries.

ll -h /usr/lib64/libapr*
lrwxrwxrwx 1 root root   17 Feb  3  2009 /usr/lib64/libapr-1.so.0 ->
libapr-1.so.0.2.7
-rwxr-xr-x 1 root root 158K Mar 14  2007 /usr/lib64/libapr-1.so.0.2.7
lrwxrwxrwx 1 root root   21 Feb  3  2009 /usr/lib64/libaprutil-1.so.0 -
> libaprutil-1.so.0.2.7
-rwxr-xr-x 1 root root 116K May 24  2008 /usr/lib64/libaprutil-1.so.
0.2.7

I don't know what specific apr version these libraries belong too but
the apr libraries in my apache2 install in /usr/local/apache2 are
thus:

ll -h /usr/local/apache2/lib/libapr*
lrwxrwxrwx 1 root root   17 Oct  8 15:39 /usr/local/apache2/lib/
libapr-1.so.0 -> libapr-1.so.0.3.3
-rwxr-xr-x 1 root root 649K Oct  8 15:39 /usr/local/apache2/lib/
libapr-1.so.0.3.3
lrwxrwxrwx 1 root root   21 Oct  8 15:40 /usr/local/apache2/lib/
libaprutil-1.so.0 -> libaprutil-1.so.0.3.4
-rwxr-xr-x 1 root root 468K Oct  8 15:40 /usr/local/apache2/lib/
libaprutil-1.so.0.3.4

Question is how do I get subversion to link against the libraries in /
usr/local/apache2/lib/ instead of /usr/lib64/?

I don't think it's something done in the subversion configure script.
libtool maybe?
On Mar 3, 3:01 pm, Mike <[email protected]> wrote:
> I think I found the problem.
>
> ldd `which svn`|grep apr
>
> libaprutil-1.so.0 => /usr/lib64/libaprutil-1.so.0 (0x00002b99b9885000)
> libapr-1.so.0 => /usr/lib64/libapr-1.so.0 (0x00002b99b9aa3000)
>
> Problem is I'm specifying which apr I want to use to the configure
> script. I'm only using the path to the binaries though. Should it be a
> full path with binary name included?
>
> On Mar 3, 1:56 pm, Mike <[email protected]> wrote:
>
> > Ohhhhh. New error message. :)
>
> > Unsupported version control system "svn": "/usr/local/lib/
> > libsvn_subr-1.so.0: undefined symbol: apr_memcache_add_server"
>
> > So it looks like the library is being found now. Do you know if the
> > error that I'm getting now is related to the subversion build? Here's
> > my configure options:
>
> > ./configure --disable-keychain --disable-mod-activation --with-apr=/
> > usr/local/apache2/bin/ --with-apr-util=/usr/local/apache2/bin/ --with-
> > apxs=/usr/local/apache2/bin/apxs --with-apache-libexecdir=/usr/local/
> > apache2/lib/ --with-sasl=/usr/lib/ --with-zlib=/usr/lib/ --without-
> > serf
>
> > It's getting there. I can feel it.
>
> > On Mar 3, 12:18 pm, "Matt Caron" <[email protected]> wrote:
>
> > > >         libsvn_ra_neon-1.so.0 -> libsvn_ra_neon-1.so.0.0.0
>
> > > And here's the thing we're looking for...
>
> > > Have you tried it again since running ldconfig? And it still doesn't
> > > work? (Because if so, I'm a little stumped...)
>
> > > Can you use svn from the command line on that system without issue? Even
> > > just doing an svn co from the svn server on that machine to something in
> > > your homedir should be a reasonable test.
> > > --
> > > SIXNET - Solutions for Your Industrial Networking Challenges
> > > 331 Ushers Road, Ballston Lake, NY 12019
> > > Tel: 1.518.877.5173, Fax: 1.518.877.8346www.sixnet.com
>
>

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en.

Reply via email to