I was running into gcc-config errors when the sage_fortran script
tried to run sage_fortran.bin, which was a symbolic link to gfortran.
(In my case, it came up when the install was trying to build lapack.)
The problem is that gfortran is sensitive to the name by which it's
called, and it doesn't know what the hell `sage_fortran.bin' means. A
simple fix was to write `/usr/bin/gfortran' directly into the
sage_fortran script, and now the compilation proceeded nicely.

Separately, I'm also running into the following error compiling
cvxopt:

gcc -pthread -shared build/temp.linux-ppc-2.5/C/base.o build/
temp.linux-ppc-2.5/C/dense.o build/temp.linux-ppc-2.5/C/sparse.o -L/
home/jj/sage-2.8.12/local/lib -L/home/jj/sage-2.8.12/local/lib/gcc-lib/
i686-pc-linux-gnu/4.0.3 -lm -llapack -lblas -lf95 -o build/lib.linux-
ppc-2.5/cvxopt/base.so
/usr/lib/gcc/powerpc-unknown-linux-gnu/4.1.2/../../../../powerpc-
unknown-linux-gnu/bin/ld: cannot find -lf95

Not quite sure how to fix that one. When I create a dummy cvxopt file
in the spkg/installed directory, though, the rest of the compilation
finishes, and SAGE seems to work fine.

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@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-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~----------~----~----~----~------~----~------~--~---

Reply via email to