Bug in configure script for PPC64 machines
tg-this-will-bounce-but-I-am-subscribed-to-the-list-honest at swox.com
Mon Feb 19 23:20:03 CET 2007
"Myria" <myriachan at cox.net> writes:
The bug is in GMP's configure: it's trying to use 64-bit PowerPC assembly
code even though it detects GCC as outputting 32-bit code.
If that is a bug, then hell, GMP's configure is shock full of bugs.
But then again, since it works as documented in the Installing GMP
manual chapter, it might not be.
It should be
using 32-bit assembly code, which is why --host=powerpc-unknown-linux-gnu
works around the problem.
That's not the reason --host=powerpc-unknown-linux-gnu doesn't trigger
the kernel bug. (I realize it sounds to serious to be true that the
kernel Linux trashes user registers at random, although only in
certain circumstances. But that's the sad truth.)
Outputting 32-bit code by default is correct on
these systems, as all the other binaries are 32-bit.
You have a somewhat narrow view of correctness.
On a system that had this problem, I was able to build both in 32-bit mode
and 64-bit mod by supplying configure with the appropriate command-line
You hack around something that has a clean, documented solution.
You might want to take a good read of the section "ABI and ISA" in the
More information about the gmp-bugs