Anna Ceguerra <anna.ceguerra@xxxxxxxxxxxxx> writes: > Could the reason for this be that my processor is still 32-bit? I have a > really old machine... You need to look into what the assembler is doing, and how it is being invoked. The assembler is not a part of gcc. Ian > On 18/04/11 18/04/11 1:45 PM, "Ian Lance Taylor" <iant@xxxxxxxxxx> wrote: > >> Jonathan Wakely <jwakely.gcc@xxxxxxxxx> writes: >> >>>> configure:3166: checking whether the C compiler works >>>> configure:3175: ./a.out >>>> ../../../../gcc-4.6-20110408/libgcc/configure: line 3177: ./a.out: Bad CPU >>>> type in executable >>> >>> I'm not sure what this error means - do you have a working gcc >>> installed that can actually compile successfully for your system? >> >> This is when building libgcc. It means that the newly built gcc is >> unable to build an executable which runs on the current system. An >> error like "Bad CPU type" suggests a problem with the assembler or with >> how gcc is invoking the assembler. I don't know enough about Darwin to >> know what is happening. >> >> Ian
