#12647: Add support for a "sagerc" script
----------------------------------+-----------------------------------------
Reporter: jdemeyer | Owner: leif
Type: enhancement | Status: closed
Priority: major | Milestone: sage-5.0
Component: scripts | Resolution: fixed
Keywords: | Work issues:
Report Upstream: N/A | Reviewers: John Palmieri
Authors: Jeroen Demeyer | Merged in: sage-5.0.beta9
Dependencies: | Stopgaps:
----------------------------------+-----------------------------------------
Comment (by leif):
Replying to [comment:20 jhpalmieri]:
> Replying to [comment:19 leif]:
> > The patch to `sage-env` causes a beta9 regression since `CFLAGS` are
now no longer exported, which at least some spkgs relied on (i.e., their
`spkg-install` sets or modifies them, but doesn't export them by itself
since this used to be redundant).
>
> Can you explain that? I thought that first sage-env was run, then spkg-
install was run (via sage-spkg). So how can exporting (an empty) `CFLAGS`
in sage-env help if that variable is later modified in spkg-install?
It would have helped only if `CFLAGS` were (e.g.) set to `""` as well (if
they had been empty or unset before), which on the other hand would
currently break building the Sage library, which needs `-fno-strict-
aliasing`, which [also] comes from Python's `CFLAGS`, but only if `CFLAGS`
are '''not''' set to `""`, i.e., not set / exported at all.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12647#comment:22>
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.
