#13287: Override more compiler-related environment variables if Sage's GCC is
used
----------------------------------------------------------------------------------+
Reporter: leif
| Owner: leif
Type: defect
| Status: needs_review
Priority: minor
| Milestone: sage-5.3
Component: scripts
| Resolution:
Keywords: GCC spkg CPP FC F77 F95 Fortran compiler preprocessor
sage-env | Work issues:
Report Upstream: N/A
| Reviewers:
Authors: Leif Leonhardy
| Merged in:
Dependencies:
| Stopgaps:
----------------------------------------------------------------------------------+
Comment (by leif):
Replying to [comment:7 jdemeyer]:
> exporting `CPP` when it's not necessarily defined doesn't look like a
good idea.
Hmmm. If it's not already defined, exporting it has no effect. It may be
(defined and) empty, but in that case it originates from the "global"
environment, i.e., has been set to `""` (and already exported) by the
user, which is certainly wrong.
Any reason it doesn't get a default value if it's not already set in
`sage-env` (like `CC`, but also `AR`, `RANLIB` etc.)?
I could either add the latter, or maybe only export `CPP` if we set it
there (`if [ -x ... ]`).
The whole thing looks a bit inconsistent, but spkgs may rely on the other
variables being defined, so I'd prefer to also let `CPP` always have a
value.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13287#comment:8>
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.
