You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "Bruce A. Mah" <bm...@acm.org> on 2004/07/16 04:35:33 UTC

RE: FS FileSystem and FreeBSD (resend)

On Thu, 2004-07-15 at 19:17, Steve wrote:
> > That's a FreeBSD Port specific problem, and use of FSFS instead of BDB 
> > will not make any difference.  We still link against apr-util, so you'll 
> > still need that library.
> 
> I kind of figured as much. Oh well, thanks for the answer.

Hmmm.  I've seen this problem on my systems, however the port installed
fine.  The problem I saw was that at run-time (i.e. trying to invoke any
of the subversion executables) the dynamic linker was complaining about
not finding the libapr shared library.  (Sorry, I don't have a record of
exactly what the error was.)

My two repository servers are running 4.10-STABLE.  Port revisions as
follows:

apache-2.0.50                       =   up-to-date with port
subversion-1.0.5                    =   up-to-date with port

Build arguments:

'devel/subversion' => 'WITH_MOD_DAV_SVN=yes WITH_SVNSERVE_WRAPPER=yes'
'www/apache2' => 'WITH_BERKELEYDB=db42'

...argh.  While I was trying to get all the information togther to
document what I thought was a reasonable workaround, I discovered that I
had an extra copy of the libapr libraries (built along with apache2)
that portupgrade stashed away for backward compatibility.  That's bound
to make a difference in some bizarre way.

Anyways.  One possible workaround is to do "ldconfig -m
/usr/local/lib/apache2".  I think this was alluded to in PR 67130 as an
ugly hack, but I don't care...I need to keep a couple of repositories
working.

I'm off to go try to understand what's going on with my two repository
servers now...like why they're working at all.  :-p

Bruce.