#11616: Upgrade MPIR to a more recent upstream release
----------------------------------------------------------------------------------------------------------------+
Reporter: leif
| Owner: leif
Type: enhancement
| Status: closed
Priority: blocker
| Milestone: sage-5.0
Component: packages
| Resolution: fixed
Keywords: sd32, GMP, SandyBridge, Westmere, yasm re2c race condition,
Linux ia64 Itanium GCC 4.7.0 bug | Work issues:
Report Upstream: N/A
| Reviewers: Jeroen Demeyer, Leif
Leonhardy, Volker Braun
Authors: Leif Leonhardy, Jeroen Demeyer
| Merged in: sage-5.0.rc0
Dependencies:
| Stopgaps:
----------------------------------------------------------------------------------------------------------------+
Comment (by leif):
Replying to [comment:69 vbraun]:
> I think this ticket shows that there is a need for a better management
of C(XX)FLAGS in Sage. Ideally via some shell script that is part of Sage,
so that not every spkg has to reinvent the wheel. The whole approach of
parsing the install of another spkg to recreate its CFLAGS is just wrong
[...]
See #12890 for a partial reply.
[[BR]]
W.r.t. "parsing the install of another spkg":
No spkg does this. Some use preprocessor variables defined in other
[s]pkgs' C headers, some use Python files of another, or use Python's
`Makefile` settings through distutils, some even link to another's library
and call functions for that purpose, others e.g. use `pkgconfig`. Whether
MPFR's, MPC's and GMP-ECM's (upstream) behaviour is ''appropriate for
Sage'' has already been discussed elsewhere.
The specific problem with MPIR (similar to those with MPFR etc.) simply is
that it by default doesn't allow to '''add''' or override ''some''
`CFLAGS`. Therefore we have to cheat it by feeding it with its own,
slightly modified flags after doing a "dry" build (i.e., running
`configure` once just to see what flags it otherwise would use).
What Jeroen calls "good `CFLAGS`" are basically `-march=...`(-related)
parameters. Also depending on MPIR's age (especially within Sage), these
aren't always optimal. Further, most of MPIR is implemented in assembly
language, where `CFLAGS` are almost completely irrelevant.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11616#comment:78>
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.
