#13137: upgrade MPIR to 2.6.0
----------------------------------------------------+-----------------------
Reporter: jhpalmieri | Owner: tbd
Type: enhancement | Status:
needs_review
Priority: major | Milestone: sage-5.6
Component: packages | Resolution:
Keywords: mpir spkg | Work issues:
Report Upstream: N/A | Reviewers: Jeroen
Demeyer
Authors: John Palmieri, Jean-Pierre Flori | Merged in:
Dependencies: #13755 | Stopgaps:
----------------------------------------------------+-----------------------
Comment (by leif):
Replying to [comment:46 leif]:
> Replying to [comment:45 jpflori]:
> > A priori, I did not modify the configure file except for the few lines
involved by the fix, so this is strange.
>
> All files in the p2 except `configure` are vanilla 2.6.0 again
(especially `config.guess`)?
>
> Another reason for the difference ''might'' be him setting `ABI=32`
manually inbetween (which should matter only in the plain MPIR builds, as
`spkg-install` does this as well, always on MacOS < 10.6 I think).
I probably just confused the output of `config.guess` and `-march=...`; in
his recent logs we have:
`configure` run "manually", Apple GCC 4.0.1:
{{{
checking build system type... nehalem-apple-darwin9.8.0
...
checking ABI=32
checking compiler gcc -m32 -O2 -fomit-frame-pointer ... yes
checking compiler gcc -m32 -O2 -fomit-frame-pointer has sizeof(long)==4...
yes
checking compiler gcc -m32 -O2 -fomit-frame-pointer -mtune=corei7... no
checking compiler gcc -m32 -O2 -fomit-frame-pointer -mtune=core2... no
checking compiler gcc -m32 -O2 -fomit-frame-pointer -mtune=nocona... yes
checking compiler gcc -m32 -O2 -fomit-frame-pointer -mtune=nocona
-march=corei7... no
checking compiler gcc -m32 -O2 -fomit-frame-pointer -mtune=nocona
-march=core2... no
checking compiler gcc -m32 -O2 -fomit-frame-pointer -mtune=nocona
-march=nocona... yes
...
using ABI="32"
CC="gcc -std=gnu99"
CFLAGS="-m32 -O2 -fomit-frame-pointer -mtune=nocona -march=nocona"
CPPFLAGS=""
MPN_PATH=" x86/applenopic generic"
...
}}}
`configure` run "manually", Apple GCC 4.2.1:
{{{
checking build system type... nehalem-apple-darwin9.8.0
...
checking ABI=32
checking compiler gcc -m32 -O2 -fomit-frame-pointer ... yes
checking compiler gcc -m32 -O2 -fomit-frame-pointer has sizeof(long)==4...
yes
checking compiler gcc -m32 -O2 -fomit-frame-pointer -mtune=corei7... no
checking compiler gcc -m32 -O2 -fomit-frame-pointer -mtune=core2... yes
checking compiler gcc -m32 -O2 -fomit-frame-pointer -mtune=core2
-march=corei7... no
checking compiler gcc -m32 -O2 -fomit-frame-pointer -mtune=core2
-march=core2... yes
...
using ABI="32"
CC="gcc -std=gnu99"
CFLAGS="-m32 -O2 -fomit-frame-pointer -mtune=core2 -march=core2"
CPPFLAGS=""
MPN_PATH=" x86/applenopic generic"
...
}}}
MPIR 2.6.0.p2 (with `sage -i ...`, Apple GCC 4.2.1, build 5577):
{{{
...
Settings chosen by MPIR when configuring with CFLAGS unset:
CC: gcc -std=gnu99
CFLAGS: -m32 -O2 -fomit-frame-pointer -mtune=core2 -march=core2
...
Finally using the following settings:
CC=gcc
CFLAGS=-m32 -O2 -fomit-frame-pointer -mtune=core2 -march=core2 -g
...
checking build system type... nehalem-apple-darwin9.8.0
...
checking ABI=32
checking compiler gcc -m32 -O2 -fomit-frame-pointer -mtune=core2
-march=core2 -g ... yes
...
using ABI="32"
CC="gcc -std=gnu99"
CFLAGS="-m32 -O2 -fomit-frame-pointer -mtune=core2 -march=core2 -g
"
CPPFLAGS=""
CXX="g++"
CXXFLAGS=""
MPN_PATH=" x86/applenopic generic"
...
}}}
(Looks like our first "dry" `configure` run influences the second; we
should probably delete some more cache files...)
And FWIW, the `-std=gnu99` still(?) gets dropped in the first place at
least, for whatever reason. (It was a long-lasting MPIR bug that `gmp.h`
-- in contrast to `mpir.h` -- was lacking this in the definition of
`__GMP_CC`.)
Also, IMHO `CXXFLAGS` shouldn't be empty. And it doesn't look like yasm's
`configure` would pick up the settings from MPIR's...
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13137#comment:47>
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.
