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

Re: back-end fsfs DB corruption? - attempt to merge uncovering it

From: Paul Hammant <paul_at_hammant.org>
Date: Tue, 15 Sep 2009 15:56:34 -0500

> You can use ldd to see which libraries your svn binary is using.
> It should only use libsvn_* libraries from the --prefix you specified
> to the configure script when building Subversion.
> If it is using any libraries e.g from /usr/lib and you did not pass
> --prefix=/usr/lib, you likely have this problem. Since all your
> libraries
> are 1.6.x versions, Subversion will run just fine; the ABI does not
> change
> at all within a single release line. But your svn 1.6.6 will behave
> like
> e.g. 1.6.5 in some places.
> You can adjust the run-time search path for shared libraries as well
> by tweaking the LD_LIBRARY_PATH environment variable. See the man page
> of ld.so for details: man ld.so
> This way you may be able to enforce use of the correct set of shared
> libraries without having to recompile:
> export LD_LIBRARY_PATH=/my/svn/prefix/lib:$LD_LIBRARY_PATH

We rebuild with --prefix pointing to the root of the libsvn_*

It is the same though, it halts at the same file.

- Paul


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-15 22:57:55 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.