Changes between Version 39 and Version 45 of Ticket #11616
- Timestamp:
- 04/09/12 10:57:13 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #11616
-
Property
Status
changed from
needs_work
toneeds_review
-
Property
Authors
changed from
Leif Leonhardy
toLeif Leonhardy, Jeroen Demeyer
-
Property
Reviewers
changed from
to
Jeroen Demeyer
-
Property
Priority
changed from
major
toblocker
-
Property
Status
changed from
-
Ticket #11616 – Description
v39 v45 5 5 The following '''new spkgs''' are based on the latest MPIR 2.1.3 spkg, the p9 from #12131: 6 6 7 '''New spkg:''' [http://boxen.math.washington.edu/home/leif/Sage/spkgs/mpir-2.4.0.p2.spkg] 8 9 '''md5sum:''' `c9e6d8e2f5de4a09b4b16ee2354a9e17 mpir-2.4.0.p2.spkg` 7 '''New spkg:''' [http://boxen.math.washington.edu/home/jdemeyer/spkg/mpir-2.4.0.p2.spkg] 10 8 11 9 (Preliminary; changes not yet committed.) … … 17 15 18 16 19 20 === mpir-2.4.0.p2 (Leif Leonhardy, April 4th, 2012) === 17 === mpir-2.4.0.p2 (Leif Leonhardy, Jeroen Demeyer, April 9th, 2012) === 21 18 #11616 (upgrading MPIR), further fixes: 22 * Before enabling `-march=native`, minimalistically check whether the23 system's assembler also understands the instructions the compiler emits24 with that option. (Work-around for e.g. GCC 4.6.3 on MacOS X 10.x and25 Intel Core i7-family CPUs with AVX.)26 * Do not unconditionally unset `PYTHON`, since Sage (>=5.0.beta10) no longer27 pollutes the environment with its package version variables, which previous-28 ly confused yasm's `configure`.29 * Fix extraction of `__GMP_CC` and `__GMP_CFLAGS` from `gmp.h`, since MPIR30 meanwhile defines these to preprocessor variables (rather than literals).31 Also don't use `\+` in `sed` patterns, as this is less portable.19 * When the first configure run (with CFLAGS unset) of MPIR fails, bail 20 out with an error. I am not aware of any system where MPIR fails 21 to configure with CFLAGS unset but succeeds with CFLAGS set. 22 -- Jeroen Demeyer 23 This implies the following simplifications: 24 - We no longer read CC and CFLAGS from /usr/include/gmp.h or 25 /usr/local/include/gmp.h 26 - We no longer try to add -march=native, we simply use MPIR's flags. 27 * Extract $CC and $CFLAGS from Makefile instead of mpir.h, which is 28 simpler and more reliable. 32 29 * Work around GCC 4.7.0 bug (compilation error) on Linux ia64 (Itanium) by 33 30 almost completely disabling optimization on that platform if GCC 4.7.x … … 40 37 * Fix a potential race condition in yasm's build by patching the re2c source. 41 38 Cf. #11844. 39 * Added `quote_asm.patch` to add proper quoting to the m4 in .asm files. 42 40 * Add "`patch` loop" to apply any patches (`*.patch`) located in `patches/`. 43 Currently only the re2c patch matches that; the prepatched header to support 44 Sun's C compiler is still copied over (and only on SunOS, although it doesn't 45 do any harm on other platforms). 41 Use this to patch gmp-h.in instead of copying the file. 46 42 * Minor clean-up; e.g. redirect error messages and warnings to `stderr`, 47 43 quote parameter to `--libdir`, add some comments and messages, also save 48 44 user's setting of `LDFLAGS` and `ABI`. 49 50 45 51 46 === mpir-2.4.0.p1 (Leif Leonhardy, March 21st, 2012) === … … 61 56 ---- 62 57 63 This fixes also: #11844 reports a potential race condition due to yasm when building MPIR in parallel. We've never run into this [before] though. The MPIR 2.4.0.'''p2''' spkg now includes a patch to upstream fixing that. 58 This fixes also: 59 60 1. #11844: a potential race condition due to yasm when building MPIR in parallel. We've never run into this [before] though. The MPIR 2.4.0.'''p2''' spkg now includes a patch to upstream fixing that. 61 62 2. #12782: when building MPIR to bootstrap GCC (i.e. when SAGE_BUILD_TOOLCHAIN=yes), do not build the C++ interface (and not the static library). This would allow to build Sage on systems which have a C compiler but not a C++ compiler. 64 63 65 64 ----