execution fault

[Chris Atwood]

It does, on both machines output is
****
librsync.so.1 => /usr/local/lib/librsync.so.1 (0x40011000)
libc.so.6 => /lib/libc.so.6 (0x4001c000)
libpopt.so.0 => /usr/lib/libpopt.so.0 (0x4014c000)
libbz2.so.1.0 => /usr/lib/libbz2.so.1.0 (0x40154000)
libz.so.1 => /usr/lib/libz.so.1 (0x40165000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
****
on both machines, though the 0x numbers are different.

Thank so much for you assistance.  Any other ideas?

  - Chris

On Thursday, September 19, 2002, at 01:47 AM, Ben Escoto wrote:
>
>   CA> In /usr/local/lib there is a sym link librsync.so.1 pointing to
>   CA> librsync.so.1.0.1 on both machines.
>
>   CA> And, rdiff does work on both machines.
>
> Hmm, I dunno...  How about
>
> ldd /usr/lib/python2.2/site-packages/rdiff_backup/_librsync.so
>
> ?  Does it correctly list /usr/local/lib/librsync.so.1?
>
>
> -- 
> Ben Escoto
> <mime-attachment>