Changes between Initial Version and Version 1 of Ticket #11896


Ignore:
Timestamp:
10/05/11 03:12:08 (11 years ago)
Author:
leif
Comment:

Would be nice if one of you could review this.

For testing, it should be sufficient to (try to) install the spkg with an arbitrary Sage version (of course installed on some 32-bit Linux running on a 64-bit processor): 

$ unset ABI # We want to test that the spkg works *without* setting it.
$ env SAGE_CHECK=yes ./sage -i http://sage.math.washington.edu/home/leif/Sage/spkgs/mpir-2.1.3.p5.spkg

After that, you should reinstall the original MPIR spkg from your Sage installation (with ./sage -f spkg/standard/mpir-<version>.spkg) in case you used a Sage version prior to Sage 4.7.2.alpha3 (into which the MPIR 2.1.3.p4 spkg from #8664, the first 2.x version in Sage, was merged).

(No need to uninstall it from Sage 4.7.2.alpha3 or if you happen to have already installed the MPIR 2.1.3.p4 spkg, the GMP-ECM 6.3.p2 spkg and the necessary patches from their tickets.)

You can of course in addition test the spkg on other (64-bit) platforms as well... :-)

Thanks!

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #11896

    • Property Cc ncohen ddrake strogdon added
    • Property Status changed from new to needs_review
    • Property Reporter changed from leif to Nathann Cohen, Dan Drake, Steve Trogdon

  • Ticket #11896 – Description

    initial v1  
    22
    33The simple solution is to set `ABI=32` in this case, which the new spkg now does (on Linux, where the issue occurred). It also sets `ABI=64` if the operating system supports it, and `ABI` isn't already set, and prints according messages.
     4
     5----
     6
     7'''New spkg:''' [http://sage.math.washington.edu/home/leif/Sage/spkgs/mpir-2.1.3.p5.spkg]
     8
     9'''md5sum:''' `7881a45bb797665f4f264e17fdab2aa5`