Hi Kevin, >>>>>>>> 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 >>>>>>> >>>>> Some type of PowerPC vs x86 thing? Can you use the file command to >>>>> make sure that the architecture matches what you are running on? >>>>> >>>> I can't seem to find the file a.out anywhere... >>>> >>> It is something that configure creates. Try looking in the config.log >>> in the libgcc directory of your obj dir. It is in the top level under >>> the <machine type> dir. >>> >> It's trying to generate from conftest.c, which I can't find either. Here is > > Check the libgcc config.log file. Doesn't it put the source code for > its test file in there if the test fails? > No I don't see any source code in there... >> >>> Try to assemble this: >>> >>> ./xgcc -B. -v simple.s >>> >>> If that works, try: >>> >>> file simple.o >> I had to do file a.out, and the result is: >> a.out: Mach-O executable i386 >>> > What happens if you try to run this: > > ./a.out It completes successfully > >>> One of your other posts, which I missed somehow, you state that your >>> system is 32-bit? I thought all of the x86 macs were 64-bit capable? >>> >> This machine was purchased in March 2006, shortly after the switch was made >> from PowerPC to Intel processors for MacBook Pros. This laptop has Intel >> Core Duo (not Core 2 Duo, which I believe is a 64-bit processor). >> > a Core Duo is 32-bit? I did not know that? Yes - I saw this on the wikipedia page for intel processors Regards, Anna.
