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] _______________________________________________ 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
