On 09/12/10 01:07 AM, kcrisman wrote:
a) why sage used g95 in the first place (yes I know it's smaller, but
it's not standard at all imho)
Agreed. I can't see the point of it.
Apparently because there was no gfortran for certain platforms. Now we
assume Linuces (?) have this, but as Dima demonstrates, with OS X
10.4, somehow this is not so easy to remove. Interestingly, he gets
stuck at Scipy apparently because of numpy, which is also the problem
on one of the tickets in question (though for a newer versino of each
of those).
- kcrisman
OK. But IMHO, using 'FC' as a variable for the Fortran compiler would be more
sensible. Then just set
FC=g95
export FC
or whatever you chose to use. The Fortran package is Sage is ill thought out.
I've tried building Sage with Sun's compiler. It fails, due to the GNU-infested
C/C++/Fortran in Sage. But ultimately it should be possible to set an
environment variable to specify the compiler. We just happen to use a
non-standard name for something which has a widely used name (FC).
Is there any reason whatsoever to have g95 code in ATLAS, given we don't build
ATLAS on OS X?
Dave
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
