Hi all,

I have trouble compiling sage on my linux box which is as follow:
x86 (amd athlon - definitely not amd64)
distro is gentoo up to date as of last week. kernel 2.6.23, glibc
2.6.1
gcc-4.2.2, binutils-2.18.
The problem I have is in the compilation of sage itself more precisely
libcsage.

Here is the last message:
sage: Building and installing modified SAGE library files.


Installing c_lib
gcc -o src/convert.os -c -O2 -g -fPIC -I/home/francois/Work/Gentoo/
sage-2.9.1.1/local/include
-I/home/francois/Work/Gentoo/sage-2.9.1.1/local/include/python2.5 -I/
home/francois/Work/Gentoo/sage-2.9.1.1/local/include/NTL -Iinclude
src/convert.c
gcc -o
src/interrupt.os -c -O2 -g -fPIC -I/home/francois/Work/Gentoo/
sage-2.9.1.1/local/include -I/home/francois/Work/Gentoo/sage-2.9.1.1/
local/include/python2.5 -I/home/francois/Work/Gentoo/sage-2.9.1.1/
local/include/NTL -Iinclude
src/interrupt.c
gcc -o
src/mpn_pylong.os -c -O2 -g -fPIC -I/home/francois/Work/Gentoo/
sage-2.9.1.1/local/include -I/home/francois/Work/Gentoo/sage-2.9.1.1/
local/include/python2.5 -I/home/francois/Work/Gentoo/sage-2.9.1.1/
local/include/NTL -Iinclude
src/mpn_pylong.c
gcc -o
src/mpz_pylong.os -c -O2 -g -fPIC -I/home/francois/Work/Gentoo/
sage-2.9.1.1/local/include -I/home/francois/Work/Gentoo/sage-2.9.1.1/
local/include/python2.5 -I/home/francois/Work/Gentoo/sage-2.9.1.1/
local/include/NTL -Iinclude
src/mpz_pylong.c
gcc -o
src/stdsage.os -c -O2 -g -fPIC -I/home/francois/Work/Gentoo/
sage-2.9.1.1/local/include -I/home/francois/Work/Gentoo/sage-2.9.1.1/
local/include/python2.5 -I/home/francois/Work/Gentoo/sage-2.9.1.1/
local/include/NTL -Iinclude
src/stdsage.c
gcc -o
src/gmp_globals.os -c -O2 -g -fPIC -I/home/francois/Work/Gentoo/
sage-2.9.1.1/local/include -I/home/francois/Work/Gentoo/sage-2.9.1.1/
local/include/python2.5 -I/home/francois/Work/Gentoo/sage-2.9.1.1/
local/include/NTL -Iinclude
src/gmp_globals.c
g++ -o
src/ZZ_pylong.os -c -fPIC -I/home/francois/Work/Gentoo/sage-2.9.1.1/
local/include -I/home/francois/Work/Gentoo/sage-2.9.1.1/local/include/
python2.5 -I/home/francois/Work/Gentoo/sage-2.9.1.1/local/include/NTL -
Iinclude
src/ZZ_pylong.cpp
g++ -o
src/ntl_wrap.os -c -fPIC -I/home/francois/Work/Gentoo/sage-2.9.1.1/
local/include -I/home/francois/Work/Gentoo/sage-2.9.1.1/local/include/
python2.5 -I/home/francois/Work/Gentoo/sage-2.9.1.1/local/include/NTL -
Iinclude
src/ntl_wrap.cpp
ld -o libcsage.so -shared -no_archive src/convert.os src/interrupt.os
src/mpn_pylong.os src/mpz_pylong.os src/stdsage.os src/gmp_globals.os
src/ZZ_pylong.os
src/ntl_wrap.os -L/home/francois/Work/Gentoo/sage-2.9.1.1/local/lib -
lntl -lgmp -lpari
ld: cannot find -lpari
scons: *** [libcsage.so] Error 1

========================

I poked around a bit and the problem is not with pari. The problem
is the parameter "-no_archive". My version of ld from binutils-2.18
doesn't
support such an option. In fact if it did, it should be --no_archive
as it is
the option can be interpreted as -n -o _archive and if I try to issue
it
again I end up with a file called _archive and a message about
creating an
archive containing DT_TEXTREL symbols.

Removing the -no_archive gives a normal result. Unfortunately I don't
know how
to resume the compilation process correctly from there as scons behave
very
differently from make.

I don't where to patch things so that it doesn't happen in the first
place. I
cannot find anything about this parameter in the SConstruct file or
spkg-install. I don't know where to look from there.

Things did go normally with sage 2.8.12 the first I compiled, I first
had the
problem trying to compile 2.8.15 and ever since. I didn't try 2.8.13.
or .14.

Any idea?

Cheers from New Zealand,
Francois

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---

Reply via email to