#8664: Upgrade Sage's MPIR spkg to version 2.1.3
---------------------------------------------------------------------------------------------------------+
Reporter: was
| Owner: GeorgSWeber
Type: enhancement
| Status: needs_review
Priority: major
| Milestone: sage-4.7.1
Component: packages
| Resolution:
Keywords: GMP ECM execstack Fedora 14 extension module library
dependencies Darwin 11 MacOS X 10.7 | Work_issues:
Upstream: N/A
| Reviewer: Leif Leonhardy, Dmitrii Pasechnik
Author: Mike Hansen, Leif Leonhardy
| Merged:
Dependencies: #5847
|
---------------------------------------------------------------------------------------------------------+
Comment(by leif):
Ok, to ease testing, I've uploaded a [http://spkg-
upload.googlecode.com/files/sage-4.7.1.rc0-8664-5847.spkg Sage 4.7.1.rc0
library spkg] with both patches (from here and #5847) already applied.
You can either build Sage 4.7.1.rc0 from scratch with these three spkgs,
or take a Sage 4.7.1.rc0 installation and just install them, automatically
rebuilding (only) the dependent spkgs.
1. Copy [http://spkg-upload.googlecode.com/files/mpir-2.1.3.p4.spkg the
MPIR spkg] and [http://spkg-upload.googlecode.com/files/ecm-6.3.p2.spkg
the GMP-ECM spkg] into `$SAGE_ROOT/spkg/standard/`.
1. '''Replace''' the `sage-4.7.1.rc0.spkg` with [http://spkg-
upload.googlecode.com/files/sage-4.7.1.rc0-8664-5847.spkg this one] (i.e.,
copy it to `$SAGE_ROOT/spkg/standard` and '''delete''' the original since
`newest_version` would otherwise take the wrong one).
1. Build:
* For a build from scratch, simply type `make`.
* For rebuilding an existing installation with the new spkgs, type
{{{
#!sh
env SAGE_UPGRADING=yes make
}}}
Note that you currently must not set `SAGE_CHECK` to `yes` in the above
procedures, since the test suite of our current FLINT won't build with the
new MPIR.
To run MPIR's and GMP-ECM's test suites, I'd suggest to simply reinstall
them afterwards with `env SAGE_CHECK=yes ./sage -f mpir-2.1.3.p4
ecm-6.3.p2`. Likewise, you can also play with different `CFLAGS` settings
(empty, some non-processor-specific flags, with some `-march=...` or
`-mtune=...` etc. included).
Then preferably run `make testlong` or `make ptestlong`, though both
upstream releases have IMHO already been quite excessively tested.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8664#comment:114>
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.
