gcc -v
Using built-in specs.
COLLECT_GCC=/usr/bin/gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/i686-redhat-linux/4.5.1/lto-
wrapper
Target: i686-redhat-linux
...
If one happens to have '-m32' in CFLAGS (and ABI *not* set) on such a
system, MPIR fails to build, because of:
checking build system type... core2-pc-linux-gnu
checking host system type... core2-pc-linux-gnu
...
checking ABI=64
checking compiler gcc -m32 -O2 -fomit-frame-pointer -mtune=core2 -
march=core2 ... yes
[This is actually MPIR fed with its "own" CFLAGS.]
...
checking C++ compiler g++ -m32 -O2 -fomit-frame-pointer -mtune=core2 -
march=core2 ... yes
...
using ABI="64"
CC="gcc -std=gnu99"
CFLAGS="-m32 -O2 -fomit-frame-pointer -mtune=core2 -march=core2
"
CPPFLAGS=""
CXX="g++"
CXXFLAGS="-m32 -O2 -fomit-frame-pointer -mtune=core2 -
march=core2 "
MPN_PATH=" x86_64/core2 x86_64 generic"
(The latter should be MPN_PATH=" x86/core2 x86 generic", otherwise the
assembler a while later of course complains about the use of %r...
registers.)
Is this a known issue?
It's a minor one of course, but -- at least for gcc -- one could
append '-m64' to the compiler flags in the ABI=64 check such that the
generated test program will fail on 32-bit systems.
Cheers,
-leif
--
You received this message because you are subscribed to the Google Groups
"mpir-devel" 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/mpir-devel?hl=en.
