#8664: Upgrade Sage's MPIR spkg to version 2.1.3 or later
-------------------------------------------------+--------------------------
Reporter: was | Owner: GeorgSWeber
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-4.6.1
Component: packages | Keywords: GMP ECM
execstack Fedora 14
Author: Mike Hansen, Leif Leonhardy | Upstream: N/A
Reviewer: Leif Leonhardy | Merged:
Work_issues: Fix extension module dependencies |
-------------------------------------------------+--------------------------
Description changed by jdemeyer:
Old description:
> {{{
> Hi,
>
> OK, after all this, the build finally completed. The only changes I made
> were:
>
> * Updated mpir to rc3
> * patched ecm as explained here:
> http://lists.gforge.inria.fr/pipermail/ecm-
> discuss/2009-August/004070.html
> (Though this had to be slightly modified -- just search for the same
> command, which moved.)
>
> I then ran the long Sage test suite, and some tests fail.
>
> http://sage.math.washington.edu/home/wstein/build/mpir2/sage-4.3.5/testlong.log
>
> ----------------------------------------------------------------------
> The following tests failed:
>
> sage -t -long "devel/sage/doc/en/tutorial/tour_numtheory.rst"
> sage -t -long "devel/sage/doc/fr/tutorial/tour_numtheory.rst"
> sage -t -long "devel/sage/sage/modular/cusps.py"
> sage -t -long "devel/sage/sage/modular/modsym/boundary.py"
> sage -t -long "devel/sage/sage/modular/modsym/ambient.py"
> sage -t -long "devel/sage/sage/libs/pari/gen.pyx"
> sage -t -long "devel/sage/sage/rings/arith.py"
> sage -t -long "devel/sage/sage/rings/integer.pyx"
> sage -t -long
> "devel/sage/sage/rings/polynomial/multi_polynomial_ideal.py"
> sage -t -long "devel/sage/sage/tests/book_stein_ent.py"
> sage -t -long
> "devel/sage/sage/schemes/elliptic_curves/heegner.py"
> Total time for all tests: 7170.6 seconds
>
> --
>
> I looked and it appears that maybe all of these are the result of the
> XGCD behavior in MPIR changing again. Has it changed to be like GMP now?
> That would be convenient.
>
> william
> }}}
New description:
{{{
Hi,
OK, after all this, the build finally completed. The only changes I made
were:
* Updated mpir to rc3
* patched ecm as explained here:
http://lists.gforge.inria.fr/pipermail/ecm-
discuss/2009-August/004070.html
(Though this had to be slightly modified -- just search for the same
command, which moved.)
I then ran the long Sage test suite, and some tests fail.
http://sage.math.washington.edu/home/wstein/build/mpir2/sage-4.3.5/testlong.log
----------------------------------------------------------------------
The following tests failed:
sage -t -long "devel/sage/doc/en/tutorial/tour_numtheory.rst"
sage -t -long "devel/sage/doc/fr/tutorial/tour_numtheory.rst"
sage -t -long "devel/sage/sage/modular/cusps.py"
sage -t -long "devel/sage/sage/modular/modsym/boundary.py"
sage -t -long "devel/sage/sage/modular/modsym/ambient.py"
sage -t -long "devel/sage/sage/libs/pari/gen.pyx"
sage -t -long "devel/sage/sage/rings/arith.py"
sage -t -long "devel/sage/sage/rings/integer.pyx"
sage -t -long
"devel/sage/sage/rings/polynomial/multi_polynomial_ideal.py"
sage -t -long "devel/sage/sage/tests/book_stein_ent.py"
sage -t -long
"devel/sage/sage/schemes/elliptic_curves/heegner.py"
Total time for all tests: 7170.6 seconds
--
I looked and it appears that maybe all of these are the result of the XGCD
behavior in MPIR changing again. Has it changed to be like GMP now? That
would be convenient.
william
}}}
New spkg: [http://spkg-upload.googlecode.com/files/mpir-2.1.3.p0.spkg]
Testing distribution (including #5847):
[http://sage.math.washington.edu/home/jdemeyer/release/sage-4.6.1.alpha0-mpir/sage-4.6.1.alpha0-mpir.tar]
--
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8664#comment:32>
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.
