Re: [rdiff-backup-users] build problem on solaris 10, x86

Jesse Reynolds Fri, 23 Jun 2006 15:40:16 -0700

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


full output follows below.

Thanks
Jesse

[EMAIL PROTECTED] ~/src/rdiff-backup/rdiff-backup-1.0.4 $ python setup.py -- librsync-dir=/usr/local build

running build
running build_py
creating build
creating build/lib.solaris-2.10-i86pc-2.4
creating build/lib.solaris-2.10-i86pc-2.4/rdiff_backup

copying rdiff_backup/backup.py -> build/lib.solaris-2.10-i86pc-2.4/ rdiff_backup copying rdiff_backup/increment.py -> build/lib.solaris-2.10-i86pc-2.4/ rdiff_backup copying rdiff_backup/TempFile.py -> build/lib.solaris-2.10-i86pc-2.4/ rdiff_backup copying rdiff_backup/Rdiff.py -> build/lib.solaris-2.10-i86pc-2.4/ rdiff_backup copying rdiff_backup/Main.py -> build/lib.solaris-2.10-i86pc-2.4/ rdiff_backup copying rdiff_backup/connection.py -> build/lib.solaris-2.10- i86pc-2.4/rdiff_backup copying rdiff_backup/__init__.py -> build/lib.solaris-2.10-i86pc-2.4/ rdiff_backup copying rdiff_backup/Globals.py -> build/lib.solaris-2.10-i86pc-2.4/ rdiff_backup copying rdiff_backup/FilenameMapping.py -> build/lib.solaris-2.10- i86pc-2.4/rdiff_backup copying rdiff_backup/Time.py -> build/lib.solaris-2.10-i86pc-2.4/ rdiff_backup copying rdiff_backup/restore.py -> build/lib.solaris-2.10-i86pc-2.4/ rdiff_backup copying rdiff_backup/user_group.py -> build/lib.solaris-2.10- i86pc-2.4/rdiff_backup copying rdiff_backup/static.py -> build/lib.solaris-2.10-i86pc-2.4/ rdiff_backup copying rdiff_backup/regress.py -> build/lib.solaris-2.10-i86pc-2.4/ rdiff_backup copying rdiff_backup/eas_acls.py -> build/lib.solaris-2.10-i86pc-2.4/ rdiff_backup copying rdiff_backup/rpath.py -> build/lib.solaris-2.10-i86pc-2.4/ rdiff_backup copying rdiff_backup/fs_abilities.py -> build/lib.solaris-2.10- i86pc-2.4/rdiff_backup copying rdiff_backup/Security.py -> build/lib.solaris-2.10-i86pc-2.4/ rdiff_backup copying rdiff_backup/Hardlink.py -> build/lib.solaris-2.10-i86pc-2.4/ rdiff_backup copying rdiff_backup/robust.py -> build/lib.solaris-2.10-i86pc-2.4/ rdiff_backup copying rdiff_backup/rorpiter.py -> build/lib.solaris-2.10-i86pc-2.4/ rdiff_backup copying rdiff_backup/lazy.py -> build/lib.solaris-2.10-i86pc-2.4/ rdiff_backup copying rdiff_backup/metadata.py -> build/lib.solaris-2.10-i86pc-2.4/ rdiff_backup copying rdiff_backup/log.py -> build/lib.solaris-2.10-i86pc-2.4/ rdiff_backup copying rdiff_backup/SetConnections.py -> build/lib.solaris-2.10- i86pc-2.4/rdiff_backup copying rdiff_backup/statistics.py -> build/lib.solaris-2.10- i86pc-2.4/rdiff_backup copying rdiff_backup/iterfile.py -> build/lib.solaris-2.10-i86pc-2.4/ rdiff_backup copying rdiff_backup/selection.py -> build/lib.solaris-2.10-i86pc-2.4/ rdiff_backup copying rdiff_backup/librsync.py -> build/lib.solaris-2.10-i86pc-2.4/ rdiff_backup copying rdiff_backup/manage.py -> build/lib.solaris-2.10-i86pc-2.4/ rdiff_backup

running build_ext
building 'rdiff_backup.C' extension
creating build/temp.solaris-2.10-i86pc-2.4

gcc -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -Wstrict-prototypes - fPIC -I/usr/local/include/python2.4 -c cmodule.c -o build/ temp.solaris-2.10-i86pc-2.4/cmodule.o gcc -shared build/temp.solaris-2.10-i86pc-2.4/cmodule.o -o build/ lib.solaris-2.10-i86pc-2.4/rdiff_backup/C.so

building 'rdiff_backup._librsync' extension

gcc -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -Wstrict-prototypes - fPIC -I/usr/local/include -I/usr/local/include/python2.4 -c _librsyncmodule.c -o build/temp.solaris-2.10-i86pc-2.4/_librsyncmodule.o 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


   ... snip - 670 lines removed ...

rs_op_kind_names 0x9 /usr/local/lib/ librsync.a(command.o) rs_mdfour_update 0x8e2 /usr/local/lib/ librsync.a(mdfour.o) rs_mdfour_update 0x8f6 /usr/local/lib/ librsync.a(mdfour.o) rs_mdfour_update 0xa86 /usr/local/lib/ librsync.a(mdfour.o) 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


On 12/06/2006, at 2:03, Andrew Ferguson wrote:

Jesse Reynolds wrote:

First issue is that I can't use the --prefix=/usr/local option to
setup.py as detailed in the README, because aparently this option
isn't actually an option. Perhaps it used to be? Anyhow, trying

"phython setup.py --librsync-dir=/usr/local install" yields the error:


After a successful build, try the install separately:
python setup.py install --prefix=/usr/local

(I think the order matters). Rdiff-backup's setup.py (like for most

Python programs) relies heavily on the Python installation doing most of the work, so although it is a small script, it does support many options.

/sgnome/tools/x86-solaris/forte/SOS8/SUNWspro/bin/cc -i -xO4 - xspace -

xstrconst -xpentium -mr -DANSICPP -D__STDC_VERSION__=199409L -DNDEBUG
-O -I/usr/sfw/include/python2.3 -c cmodule.c -o build/
temp.solaris-2.10-i86pc-2.3/cmodule.o
unable to execute /sgnome/tools/x86-solaris/forte/SOS8/SUNWspro/bin/
cc: No such file or directory
error: command '/sgnome/tools/x86-solaris/forte/SOS8/SUNWspro/bin/cc'
failed with exit status 1

Where is this "/sgnome/tools/..." path coming from?



I believe this is coming from your Python installation. The Python
installation handles C compiler paths, flags, etc.

Try overriding it with:

CC=gcc python setup.py --librsync-dir=/usr/local install


Andrew
--
Andrew Ferguson - [EMAIL PROTECTED]


Jesse Reynolds
[EMAIL PROTECTED]
Virtual Artists Pty Ltd - 08 8223 2288 - http://www.va.com.au/

smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
rdiff-backup-users mailing list at [email protected]
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] build problem on solaris 10, x86

Reply via email to