Re: svn 1.3.0 <-> apache httpd 2.2.0

hmmm...okay, I was reading the manual with the wrong assumption. I wonder why you are forced to checkout an entire directory if you only need to work on a single file?
 
A check of my /etc/ld.so.conf file found, to my surprise, that /usr/local/lib was not included, so I added it. Not that I believe this was causing the problem, becuase every other app with dynamic lib files in /usr/local/lib runs fine. I deleted all the svn .so files from /usr/local/lib, re-downloaded a fresh svn 1.3 bz2 and resintalled it. Running make check found no failures. Then, for good measure, I rebooted linux.
 
Now.....[takes deep breath]
 
Apache httpd will not start. apachectl returns the following error:
 
    Cannot load /usr/local/apache2/modules/mod_dav_svn.so into server:
    /usr/local/apache2/modules/mod_dav_svn.so: undefined symbol: svn_fs_access_add_lock_token

I am pulling what hair I have left out. Does anybody have a clue as to what is wrong now?
 
tia,
mark

>>> Garrett Rooney <rooneg@electricjellyfish.net> 16-Feb-06 17:26 PM >>>

On 2/16/06, Mark Galbreath <GalbreathM@gao.gov> wrote:

> According to the documentation, neither of these scenarios should occur: the
> first should work and the second should fail (svn is a client-side app and
> supposedly takes only network URLs).

That's incorrect, none of the documentation should be indicating that
you can check out a single file, that's never been possible for
Subversion. Not sure what's causing your fsfs module error though.

-garrett
Received on Fri Feb 17 00:08:49 2006