On 4/21/08, mabshoff <[EMAIL PROTECTED]> wrote:
>
> > export CC=gcc-4.3
> > export CXX=g++-4.3
>
>
> I am not sure this will work all the time since sometimes we overwrite
> CC or CXX. I would suggest you put the 4.3 gcc and g++ somewhere in
> $PATH before gcc and g++ - Sage will then use them automatically.
Ok, I've switched to
export PATH=~/sage/bin:$PATH
export CC=gcc-4.3
export CXX=g++-4.3
export SAGE_FORTRAN=~/sage/bin/gfortran
export SAGE_FORTRAN_LIB=~/sage/lib/libgfortran.so
(with gcc, g++, gfortran symlinks in ~/sage/bin, and a libgfortran.so
symlink in ~/sage/lib). Maybe I'll have a look at the install.log
later to see which packages honor the env variables and which don't.
(maybe I should link gcc to /bin/false to reallly test this... ;-) )
> ATLAS only links to libgfortran.so for some reason, so either link it
> against that name or copy it somewhere as libgfortran.so and point
> SAGE_FORTRAN_LIB to it. Another alternative is to start the build and
> then copy libgfortran.so.3 into SAGE_LOCAL/lib as libgfortran.so
> before ATLAS get going.
Please consider the following patch for the readme (don't credit me, I
just reworded what you just said :-) ).
--- sage-3.0.rc0/README.txt 2008-04-19 04:32:24.000000000 -0300
+++ sage-3.0.rc1/README.txt 2008-04-21 18:58:39.000000000 -0300
@@ -67,6 +67,14 @@
export SAGE_FORTRAN=/exact/path/to/gfortran
export SAGE_FORTRAN_LIB=/path/to/fortran/libs/libgfortran.so
+ Note that ATLAS only links to libgfortran.so for some reason.
+ If your system-wide library has a different filename (e.g.
+ libgfortran.so.3), either link it against that name or copy it
+ somewhere as libgfortran.so and point SAGE_FORTRAN_LIB to it.
+ Another alternative is to start the build and then copy
+ libgfortran.so.3 into SAGE_LOCAL/lib as libgfortran.so before
+ ATLAS get going.
+
UNSUPPORTED, BUT HIGH PRIORITY TO SUPPORT SOON:
sparc Solaris 9, Solaris 10
x86_64 Solaris 10
> Well, many people seem to disagree with you ;) - some times you should
> be able to set some env variable to point it to gfortran-4.3. I think
> in the vast majority of cases configure checks for some Fortran
> compiler ever though they do not compile any Fortran code. Sigh ...
> autohell ;)
Yes, yes... but I don't know what is the analogue env variable of CC
and CXX for fortran. Is there one?
Gonzalo
--~--~---------~--~----~------------~-------~--~----~
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://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
