#13349: Deprecate SAGE_FORTRAN, support FC
----------------------------------+-----------------------------------------
Reporter: jdemeyer | Owner: tbd
Type: enhancement | Status: needs_review
Priority: critical | Milestone: sage-5.3
Component: build | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: Jeroen Demeyer | Merged in:
Dependencies: | Stopgaps:
----------------------------------+-----------------------------------------
Comment (by leif):
Replying to [comment:10 jdemeyer]:
> Replying to [comment:6 leif]:
> > It's not clear to me why you `unset FC` in case Sage's GCC is (or will
be) installed; in that case I'd just set it to `gfortran` as well, since
`$SAGE_LOCAL/bin/` comes first in the path anyway.
> If `FC` is unset, it will default to "gfortran" anyway, see how the
`sage_fortran` script is created.
At least in the long run, we should get rid of the `sage_fortran` script
as well.
If a package sees `FC` being set, it'll (hopefully) use that. If it's
unset, it'll try to guess the Fortran compiler, which might yield (Sage's)
`gfortran`, but also some other Fortran compiler which happens to be
installed on the system. (Explicitly setting `FC` etc. to `sage_fortran`
in every spkg which uses Fortran is a redundant kludge.)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13349#comment:13>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.