#12443: the sage library doesn't respect global CC and CXX flags
------------------------------+---------------------------------------------
Reporter: rohana | Owner: GeorgSWeber
Type: defect | Status: needs_review
Priority: major | Milestone: sage-5.0
Component: build | Keywords:
Work_issues: | Upstream: N/A
Reviewer: Jeroen Demeyer | Author: R. Andrew Ohana
Merged: | Dependencies:
------------------------------+---------------------------------------------
Comment(by leif):
Related, and equally important:
If `CFLAGS` are set (even to `""`), Python's `CFLAGS` are dropped, which
include `-fno-strict-aliasing`, which means that you currently always have
to manually add `-fno-strict-aliasing` when setting/modifying `CFLAGS`
(and building with GCC), since otherwise invalid code is generated for (at
least some) Cython modules.
(`-fstrict-aliasing` in contrast is ''enabled'' by most of GCC's
`O`-levels.)
----
Luckily, if you build Python with `CC` or `CXX` set, the Sage library just
picks up these settings, so I personally never had trouble with the main
topic of this ticket, while other spkgs (like Lcalc, ratpoints, zn_poly
and even Singular!) still suck...
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12443#comment:11>
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.
