I found the problem - a weird one.
At some point, someone had run crle with several -i <dir> options,
which I am guessing causes crle to load all of the libraries (not lib
dirs) found in the specified dirs in ld.so.cache. That configuration
seems to preempt ld from loading any 'new' libraries at all - regardles
of LD_LIBRARY_PATH contents.
Anyway, running crle with just -l args fixed the problem.
Sorry for the false alarm, and thanks for the reponse.
Brian
======================================================================
On Sat, Mar 11, 2006 at 01:39:38PM -0800, dean gaudet wrote:
> On Wed, 1 Mar 2006, Brian C. Hill wrote:
>
> > ImportError: ld.so.1: /usr/pkg/python/bin/rdiff-backup: fatal:
> > librsync.so.1: open failed: No such file or directory
> > -----------------------------------------------------------------
> >
> > What am I doing wrong? Is an old Python installation (this system
> > has 2.2 and 2.3) interfering?
> >
> > I am using:
> >
> > python: 2.4
> > librsync: 0.9.7
>
> are you sure librsync is where python is looking for it? i.e. the path to
> it is in /etc/ld.so.conf or in your LD_LIBRARY_PATH?
>
> -dean
--
_____________________________________________________________________
/ Brian C. Hill [EMAIL PROTECTED] http://brian.bch.net \
| UNIX Specialist BCH Technical Services http://www.bch.net |
_______________________________________________
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
