#8664: Upgrade Sage's MPIR spkg to version 2.1.1
---------------------------+------------------------------------------------
Reporter: was | Owner: GeorgSWeber
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-4.5.3
Component: packages | Keywords:
Author: Mike Hansen | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
---------------------------+------------------------------------------------
Comment(by leif):
Replying to [comment:10 leif]:
> Defining {{{SAGE_SPKG}}} to {{{sage-spkg -f}}} in
{{{spkg/standard/deps}}} should ''in principle'' also work, but doesn't...
apparently because ''not really all'' shared libraries that use
{{{libgmpxx.so}}} get rebuilt, so some still refer to the old, deleted
{{{libgmpxx.so.3}}}.
I think this could be fixed by making extension modules also depend on
(some of) the libraries they use (in {{{module_list.py}}}), with the
disadvantage that these modules would get rebuilt whenever their libraries
"change", even if the interfaces stay the same (and even if just the
modification time changed due to a rebuild/reinstallation).
----
> Rebuilding Sage 4.5.3.alpha2 with MPIR 2.1.1 and ECM 6.3 ''from
scratch'' worked on Ubuntu 10.04 x86_64 (parallel build with 32 jobs);
{{{ptestlong}}} passed all tests.
Same for Fedora 13 x86 (parallel build with 6 jobs), also {{{ptestlong}}}.
----
Unfortunately, there seems to be some incompatibility between the new PARI
(2.4.3.svn-12577.p4) or - more precisely - the required changes to Sage's
interface to PARI in order to upgrade PARI (Sage 4.6.prealpha3, see #9343
and [http://wiki.sagemath.org/NewPARI the NewPARI Wiki page]) and MPIR
2.1.1:
On Ubuntu 10.04 x86_64 (Core2, gcc 4.4.3) exactly two of all doctests
({{{ptestlong}}}) '''segfault''' (in
{{{sage/schemes/elliptic_curves/ell_point.py}}}).
On Fedora 13 x86 (Pentium 4 Prescott, gcc 4.4.4) the same two doctests and
another one in {{{ell_rational_field.py}}} segfault, and in addition one
doctest in the latter file raises an unexpected exception
({{{TypeError}}}), which seems to be the result of some other failure.
Maybe all are due to memory (or stack) corruption. See
http://trac.sagemath.org/sage_trac/ticket/9343#comment:327 ff. for
details; we haven't yet opened a separate ticket.
(For testing with Sage 4.6.prealpha3, I copied the MPIR 2.1.1 and ECM 6.3
spkgs to {{{spkg/standard}}}, and built Sage from scratch - without
problems. I also reinstalled the PARI, MPIR and ECM packages later with
{{{env SAGE_CHECK=yes ./sage -f ...}}}; all test suites passed.)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8664#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.
