#10252: ecm does not compile on some 32-bit Linux systems
------------------------+---------------------------------------------------
Reporter: jdemeyer | Owner: tbd
Type: defect | Status: new
Priority: major | Milestone: sage-4.6.1
Component: packages | Keywords: ecm spkg-install
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
------------------------+---------------------------------------------------
Comment(by leif):
Replying to [comment:8 jdemeyer]:
> I can imagine that this bug-fix will make the ecm package work, but I
believe that the deeper issue in Sage still needs to be addressed: namely
that {{{spkg-install}}} (both for mpir and for ecm) is providing CFLAGS
when it should leave that to the packages themselves.
I consider such ''upstream'' issues, i.e., upstream should IMHO
'''"modify"''' `CFLAGS` et al. if appropriate or necessary, rather than
either ignoring them or (solely) using user-specified settings "as is".
(Try e.g. {{{env CFLAGS="" ./sage -ba-force && ./sage -c "quit"}}}...
which ''breaks'' the Cython-generated C code, or at least used to do so.)
[[BR]]
> For example, on sage.math.washington.edu, the upstream mpir package uses
the flags {{{-O2 -m64 -march=core2 -mtune=core2}}} (i.e.: optimized for
the particular machine) while within Sage, the flags {{{-g -O3}}} are
used.
Just for the record: `-march=hobel` implies `-mtune=hobel` (and
`-mcpu=hobel`).
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10252#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.
