[scponly] library issues with scponlyc and subversion

Ensel Sharon user at dhp.com
Fri Jun 9 20:36:27 EDT 2006


Kaleb,

On Fri, 9 Jun 2006, Kaleb Pederson wrote:

> Ok, this is probably the root of the problem.  If you haven't already you will 
> need to create the hints file (/etc/ld.so.conf -- perhaps at a different 
> location in freebsd?) and make sure that it lists /usr/local and any other 
> lib directories that are not automatically searched.  These files are fairly 
> critical if you need shared libraries.
> 
> Once ld.so.conf is configured, then you need to get 
> `ldconfig -v -r /home -f /home/etc/ld.so.conf` to correctly list all the 
> libraries that are within the chroot (or run ldconfig from within the 
> chroot... but then you would have yet another program to copy into the 
> chroot).
> 
> > > 4) What does ldd show you when run within the chroot?
> >
> > ldd /usr/local/bin/svn | grep not
> >
> >         libaprutil-1.so.0 => not found (0x0)
> 
> Once ldconfig has been sucessfully run, all of these should go away and 
> everything should "just work" :)


Ok, I get this.

The confusing thing is, how is it that rsync and unison are working just
fine ?  I mean, they have library dependencies as well, which are in the
same locations, etc.

Why do I need to create a hints file and worry about ldconfig for
subversion, and not for rsync and unison ?




More information about the scponly mailing list