Thanks Andrew
I'm trying again now with a slightly different setup. I have
librsync 0.9.7 installed under /usr/local, eg:
/usr/local/include/librsync-config.h
/usr/local/include/librsync.h
/usr/local/lib/librsync.a
/usr/local/lib/librsync.la
/usr/local/lib/librsync.so.1
/usr/local/lib/librsync.so.1.0.2
Python is version 2.4.2, at:
/usr/local/bin/python
Now when I try and run:
python setup.py --librsync-dir=/usr/local build
The third call to gcc returns a large amount of remainint
relocations against allocatable but non-wriable sections. What does
this mean?
gcc -shared build/temp.solaris-2.10-i86pc-2.4/_librsyncmodule.o -L/
usr/local/lib -lrsync -o build/lib.solaris-2.10-i86pc-2.4/
rdiff_backup/_librsync.so
Text relocation remains referenced
against symbol offset in file
<unknown> 0xb /usr/local/lib/
librsync.a(buf.o)
<unknown> 0x23 /usr/local/lib/
librsync.a(buf.o)
<unknown> 0xb5 /usr/local/lib/
librsync.a(buf.o)
<unknown> 0xba /usr/local/lib/
librsync.a(buf.o)
<unknown> 0xd9 /usr/local/lib/
librsync.a(buf.o)
... snip ...
rs_mdfour_result 0xa98 /usr/local/lib/
librsync.a(mdfour.o)
ld: fatal: relocations remain against allocatable but non-writable
sections
collect2: ld returned 1 exit status
error: command 'gcc' failed with exit status 1