Changes between Version 49 and Version 56 of Ticket #11616


Ignore:
Timestamp:
04/10/12 05:40:52 (15 months ago)
Author:
jdemeyer
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #11616

    • Property Cc jpflori added

  • Ticket #11616 – Description

    v49 v56  
    55The following '''new spkg''' is based on the latest MPIR 2.1.3 spkg, the p9 from #12131: 
    66 
    7 '''New spkg:''' [http://boxen.math.washington.edu/home/jdemeyer/spkg/mpir-2.4.0.p2.spkg] 
     7'''New spkg:''' [http://boxen.math.washington.edu/home/jdemeyer/spkg/mpir-2.4.0.p3.spkg] 
    88 
    99(Preliminary; changes not yet committed.) 
    1010 
    11  
    12 === mpir-2.4.0.p2 (Leif Leonhardy, Jeroen Demeyer, April 9th, 2012) === 
    13  #11616 (upgrading MPIR), further fixes: 
     11=== mpir-2.4.0.p3 (Jeroen Demeyer, April 10th, 2012) === 
     12 Trac #11616, reviewer fixes: 
    1413 * When the first configure run (with CFLAGS unset) of MPIR fails, bail 
    1514   out with an error.  I am not aware of any system where MPIR fails 
    1615   to configure with CFLAGS unset but succeeds with CFLAGS set. 
    17    -- Jeroen Demeyer 
    1816   This implies the following simplifications: 
    1917   - We no longer read CC and CFLAGS from /usr/include/gmp.h or 
    … …  
    2220 * Extract $CC and $CFLAGS from Makefile instead of mpir.h, which is 
    2321   simpler and more reliable. 
     22 * Added `quote_asm.patch` to add proper quoting to the m4 in .asm files. 
     23 * Use `patch` to patch gmp-h.in instead of copying the file. 
     24 * Remove "unset PYTHON" which is not needed anymore since Trac #10492. 
     25 
     26=== mpir-2.4.0.p2 (Leif Leonhardy, April 4th, 2012) === 
     27 #11616 (upgrading MPIR), further fixes: 
     28 * Before enabling `-march=native`, minimalistically check whether the 
     29   system's assembler also understands the instructions the compiler emits 
     30   with that option.  (Work-around for e.g. GCC 4.6.3 on MacOS X 10.x and 
     31   Intel Core i7-family CPUs with AVX.) 
     32 * Do not unconditionally unset `PYTHON`, since Sage (>=5.0.beta10) no longer 
     33   pollutes the environment with its package version variables, which previous- 
     34   ly confused yasm's `configure`. 
     35 * Fix extraction of `__GMP_CC` and `__GMP_CFLAGS` from `gmp.h`, since MPIR 
     36   meanwhile defines these to preprocessor variables (rather than literals). 
     37   Also don't use `\+` in `sed` patterns, as this is less portable. 
    2438 * Work around GCC 4.7.0 bug (compilation error) on Linux ia64 (Itanium) by 
    2539   almost completely disabling optimization on that platform if GCC 4.7.x 
    … …  
    3246 * Fix a potential race condition in yasm's build by patching the re2c source. 
    3347   Cf. #11844. 
    34  * Added `quote_asm.patch` to add proper quoting to the m4 in .asm files. 
    3548 * Add "`patch` loop" to apply any patches (`*.patch`) located in `patches/`. 
    36    Use this to patch gmp-h.in instead of copying the file. 
     49   Currently only the re2c patch matches that; the prepatched header to support 
     50   Sun's C compiler is still copied over (and only on SunOS, although it doesn't 
     51   do any harm on other platforms). 
    3752 * Minor clean-up; e.g. redirect error messages and warnings to `stderr`, 
    3853   quote parameter to `--libdir`, add some comments and messages, also save 
    … …  
    4762   the potential race condition was fixed in MPIR 2.1.4. 
    4863 * Fix `.hgtags`, which contained duplicate entries, and 
    49    was missing others.  
     64   was missing others. 
    5065 
    5166---- 
    … …  
    5974---- 
    6075 
    61 Some '''old spkgs''': 
     76Some '''older spkgs''': 
    6277 
     78 * [http://boxen.math.washington.edu/home/leif/Sage/spkgs/mpir-2.4.0.p2.spkg] (based on 2.1.3.p9) [[BR]] 
     79   md5sum: `c9e6d8e2f5de4a09b4b16ee2354a9e17  mpir-2.4.0.p2.spkg` 
    6380 * [http://boxen.math.washington.edu/home/leif/Sage/spkgs/mpir-2.4.0.p1.spkg] (based on 2.1.3.p9) [[BR]] 
    6481   md5sum: `0d88b7dfe358bb429a5a9aa3a3b4b00b  mpir-2.4.0.p1.spkg` 
    65  
     82 * http://spkg-upload.googlecode.com/files/mpir-2.4.0.p0.spkg (based on 2.1.3.p4) [[BR]] 
     83   md5sum: `98e04aa43ceef04d83574f0ee8e152fc  mpir-2.4.0.p0.spkg` 
    6684 * http://spkg-upload.googlecode.com/files/mpir-2.3.1.p0.spkg (based on 2.1.3.p4) [[BR]] 
    6785   md5sum: `ff0104e302611e49604a1c4ead97cbf4  mpir-2.3.1.p0.spkg` 
    6886 
    69  * http://spkg-upload.googlecode.com/files/mpir-2.4.0.p0.spkg (based on 2.1.3.p4) [[BR]] 
    70    md5sum: `98e04aa43ceef04d83574f0ee8e152fc  mpir-2.4.0.p0.spkg` 
    71  
    72 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. 
     87The last is just intended as a "fallback" spkg in case problems should arise. 
    7388 
    7489=== mpir-2.4.0.p0 (Leif Leonhardy, July 21st, 2011) === 
    … …  
    85100---- 
    86101 
    87 [[BR]] 
    88  
    89102The 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. 
    90103 
    91 [[BR]] 
     104---- 
    92105 
    93 For instructions on how to install / test the spkgs see also #8664.  It is sufficient to just 
     106To install / test the spkg, it is sufficient to just 
    94107 
    95  * copy the spkg into `$SAGE_ROOT/spkg/standard/`, then 
     108 1. Download the new spkg and copy it into `$SAGE_ROOT/spkg/standard/`. 
    96109 
    97  * run 
     110 2. Install the MPIR spkg: 
     111{{{ 
     112#!sh 
     113$ ./sage -f spkg/standard/mpir-<version>.spkg 
     114}}} 
     115 
     116 3. Re-install all packages depending on MPIR: 
    98117{{{ 
    99118#!sh