Bug in configure script for PPC64 machines

Fuzzy Logic fuzzymo at gmail.com
Mon Feb 19 06:28:13 CET 2007

I left off the exports, and just did:

./configure --host=powerpc-unknown-linux-gnu
make check

and was successful.

So, on my PowerPC64, a build configured with:
./configure --build=none-unknown-linux-gnu works if the x86-fat patch is applied
./configure --host=powerpc-unknown-linux-gnu works without any changes
./configure fails in make check (possibly for the reasons outlined by
Myria): the log of the ./configure output was previously attached.

Hopefully, this information will help.


On 1/30/07, Myria <myriachan at cox.net> wrote:
> As "Fuzzy Logic" ran into on January 25, there is a bug in configure for
> PowerPC Linux machines.  I ran into it as well and diagnosed some of it.
> On these machines, "configure" identifies the machine type as
> powerpc64-unknown-linux-gnu.  This causes it to select the 64-bit assembly
> code.  However, GCC on these machines is set to do a 32-bit compile by
> default.  configure recognizes that GCC is 32-bit by default, but it doesn't
> switch to using the 32-bit PowerPC assembly code.  The result is that "make
> check" failed because some code is 32-bit and some code is 64-bit.  Unlike
> x86-32 and x86-64, such mixed code will compile and link.

More information about the gmp-bugs mailing list