On Fri, Feb 17, 2012 at 4:39 AM,
<address@hidden> wrote:
On 17.02.2012 01:04, Jonathan Kelley wrote:
> Just grabbed the duplicity stuff off the site, but it is not starting properly.
>
> I have pasted the output of compiling librsync with shared library support as well as the output of duplicity compile.
>
>
>
http://pastebin.com/yRnQ5sQf <--- librsync stuff
>
>
http://pastebin.com/C1A8mmk8 <---- duplicity stuff
>
>
> After installing both packages, duplicity does not work.
>
> Should've worked since /usr/local/include/librsync.h exist and such, but not sure why.
>
Please check:
was
~root/duplicity-0.6.17/build/lib.linux-x86_64-2.4/duplicity/_librsync.so
really created? the pastebin output suggests so.
is it now under
/usr/lib64/python2.4/site-packages/duplicity/_librsync.so
? if not copy it there manually and try again.
A couple of changes need to be make on the librsync install:
1) remove the --enable-shared flag
2) add --prefix=/usr
The install into /usr/local is causing the problem since /usr/local is not in the default library path.
Duplicity should now be able to find the librsync.so.1 file.
Note: a short fix is to 'sudo mv /usr/local/lib/librsync.* /usr/lib'. I'm not sure the shared option will work, but it's worth a try.
...Ken