#11616: Upgrade MPIR to a more recent upstream release
----------------------------------------------------+-----------------------
Reporter: leif | Owner: leif
Type: enhancement | Status:
needs_review
Priority: major | Milestone: sage-5.0
Component: packages | Resolution:
Keywords: sd32, GMP, SandyBridge, Westmere | Work issues:
Report Upstream: N/A | Reviewers:
Authors: Leif Leonhardy | Merged in:
Dependencies: | Stopgaps:
----------------------------------------------------+-----------------------
Changes (by {'newvalue': u'Leif Leonhardy', 'oldvalue': ''}):
* status: needs_work => needs_review
* work_issues: Rebase the spkg(s) on the MPIR 2.1.3.p9 spkg from #12131
=>
* author: => Leif Leonhardy
Old description:
> This is a follow-up to #8664.
>
> The following spkgs are based on the MPIR 2.1.3.p4 spkg from #8664:
>
> * http://spkg-upload.googlecode.com/files/mpir-2.3.1.p0.spkg [[BR]]
> md5sum: `ff0104e302611e49604a1c4ead97cbf4 mpir-2.3.1.p0.spkg`
>
> * http://spkg-upload.googlecode.com/files/mpir-2.4.0.p0.spkg [[BR]]
> md5sum: `98e04aa43ceef04d83574f0ee8e152fc mpir-2.4.0.p0.spkg`
>
> You may want to give both of them a try, although the former is just
> intended as a "fallback" spkg in case problems introduced in the latter
> should arise.
>
> '''Note:''' On '''64-bit''' processors running '''32-bit''' operating
> systems, one currently has to set `ABI=32`, otherwise the build will
> fail. This is already fixed in #11964.
>
> [[BR]]
>
> The list of changes between MPIR 2.1.3 (more precisely, 2.1.1) and MPIR
> 2.4.0 is fairly long, so I haven't put them into the description, but
> [attachment:MPIR_upstream_changes_between_2.1.1_and_2.4.0.txt attached
> them] in a plain text file.
>
> [[BR]]
>
> For instructions on how to install / test the spkgs see also #8664. It
> is sufficient to just
>
> * copy the spkg into `$SAGE_ROOT/spkg/standard/`, then
>
> * run
> {{{
> #!sh
> $ env SAGE_UPGRADING=yes make build
> }}}
> (or omit `build` to also rebuild the documentation in the same `make`
> run).
>
> To run just MPIR's test suite, you can reinstall the spkg with
> `SAGE_CHECK=yes`:
> {{{
> #!sh
> $ env SAGE_CHECK=yes ./sage -f spkg/standard/mpir-<version>.spkg
> }}}
> Or, if you haven't yet installed the spkg (but copied it into
> `$SAGE_ROOT/spkg/standard/` as mentioned above), do:
> {{{
> #!sh
> $ env SAGE_CHECK=yes ./sage -i spkg/standard/mpir-<version>.spkg
> $ env SAGE_UPGRADING=yes make build # rebuilds all dependent packages
> }}}
> Afterwards you can run `make doc` to (re)build the documentation, and /
> or `make ptestlong` to run Sage's full test suite in parallel.
>
> ----
>
> Slightly related: #11844 reports a potential race condition due to yasm
> when building MPIR in parallel. We've never run into this [before]
> though.
>
> ----
>
> === mpir-2.4.0.p0 (Leif Leonhardy, July 21st, 2011) ===
> * Upstream upgrade to MPIR 2.4.0 (#11616).
>
> === mpir-2.3.1.p0 (Leif Leonhardy, July 20th, 2011) ===
> * Upstream upgrade to MPIR 2.3.1 (#11616).
> * Clean up .hgtags.
>
> === mpir-2.1.3.p4 (Leif Leonhardy, July 19th, 2011) ===
> * #8664: Upgrade Sage's MPIR spkg to version 2.1.3 [[BR]]
> ...
New description:
This is a follow-up to #8664 (and a couple of other tickets).
[[BR]]
The following new spkg is based on the latest MPIR 2.1.3 spkg, the p9 from
#12131:
'''New spkg:'''
[http://boxen.math.washington.edu/home/leif/Sage/spkgs/mpir-2.4.0.p1.spkg]
'''md5sum:''' `0d88b7dfe358bb429a5a9aa3a3b4b00b mpir-2.4.0.p1.spkg`
=== mpir-2.4.0.p1 (Leif Leonhardy, March 21st, 2012) ===
* Upstream upgrade to MPIR 2.4.0 (#11616).
The 2.4.0.p0 spkg isn't in this history, as it was based
on the 2.1.3.p4 spkg, i.e., is "on another branch",
and never got merged into Sage.
* Remove forcing a sequential `make install` again, since
the potential race condition was fixed in MPIR 2.1.4.
* Fix `.hgtags`, which contained duplicate entries, and
was missing others.
----
The following spkgs are based on the MPIR 2.1.3.p4 spkg from #8664:
* http://spkg-upload.googlecode.com/files/mpir-2.3.1.p0.spkg [[BR]]
md5sum: `ff0104e302611e49604a1c4ead97cbf4 mpir-2.3.1.p0.spkg`
* http://spkg-upload.googlecode.com/files/mpir-2.4.0.p0.spkg [[BR]]
md5sum: `98e04aa43ceef04d83574f0ee8e152fc mpir-2.4.0.p0.spkg`
You may want to give both of them a try, although the former is just
intended as a "fallback" spkg in case problems introduced in the latter
should arise.
'''Note:''' On '''64-bit''' processors running '''32-bit''' operating
systems, one currently has to set `ABI=32`, otherwise the build will fail.
This is already fixed in #11964.
[[BR]]
The list of changes between MPIR 2.1.3 (more precisely, 2.1.1) and MPIR
2.4.0 is fairly long, so I haven't put them into the description, but
[attachment:MPIR_upstream_changes_between_2.1.1_and_2.4.0.txt attached
them] in a plain text file.
[[BR]]
For instructions on how to install / test the spkgs see also #8664. It is
sufficient to just
* copy the spkg into `$SAGE_ROOT/spkg/standard/`, then
* run
{{{
#!sh
$ env SAGE_UPGRADING=yes make build
}}}
(or omit `build` to also rebuild the documentation in the same `make`
run).
To run just MPIR's test suite, you can reinstall the spkg with
`SAGE_CHECK=yes`:
{{{
#!sh
$ env SAGE_CHECK=yes ./sage -f spkg/standard/mpir-<version>.spkg
}}}
Or, if you haven't yet installed the spkg (but copied it into
`$SAGE_ROOT/spkg/standard/` as mentioned above), do:
{{{
#!sh
$ env SAGE_CHECK=yes ./sage -i spkg/standard/mpir-<version>.spkg
$ env SAGE_UPGRADING=yes make build # rebuilds all dependent packages
}}}
Afterwards you can run `make doc` to (re)build the documentation, and / or
`make ptestlong` to run Sage's full test suite in parallel.
----
Slightly related: #11844 reports a potential race condition due to yasm
when building MPIR in parallel. We've never run into this [before] though.
----
=== mpir-2.4.0.p0 (Leif Leonhardy, July 21st, 2011) ===
* Upstream upgrade to MPIR 2.4.0 (#11616).
=== mpir-2.3.1.p0 (Leif Leonhardy, July 20th, 2011) ===
* Upstream upgrade to MPIR 2.3.1 (#11616).
* Clean up .hgtags.
=== mpir-2.1.3.p4 (Leif Leonhardy, July 19th, 2011) ===
* #8664: Upgrade Sage's MPIR spkg to version 2.1.3 [[BR]]
...
--
Comment:
It's not unlikely that I'll soon provide an MPIR 2.4.0.p2 spkg, also
fixing a potential race condition in the `yasm` build, as well as an
"experimental" MPIR 2.5.1 spkg.
Please build, test, and review!
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11616#comment:14>
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.
