On Sat, May 1, 2010 at 8:35 AM, Tom Hawkins <tomahawkins@xxxxxxxxx> wrote: > On Sat, May 1, 2010 at 8:28 AM, Tom Hawkins <tomahawkins@xxxxxxxxx> wrote: >> On Sat, May 1, 2010 at 2:06 AM, Ian Lance Taylor <iant@xxxxxxxxxx> wrote: >>> >>> Run the failing gcc command with the -v option to >>> see which assembler it is invoking. It appears that your host gcc is >>> running your target assembler, which is a peculiar failure mode. >> >> With -v, yes, it looks like it is using the target assembler. Any suggestions? > > There is an 'as' in the build directory when the gcc command in > question is run. And --version confirms it is the target assembler. > > I have '.' in my PATH by default. Is this a problem? > Removing '.' from my PATH appears to fixed the assembler problem. The next issue is a configuring problem in powerpc-eabi/libada. Why does it think the host system is powerpc-unknown-eabi and not i686-pc-linux-gnu? Checking multilib configuration for libada... mkdir -p -- powerpc-eabi/libada Configuring in powerpc-eabi/libada configure: creating cache ./config.cache checking build system type... i686-pc-linux-gnu checking host system type... powerpc-unknown-eabi checking target system type... powerpc-unknown-eabi checking for powerpc-eabi-gcc... /home/e0082888/Downloads/build/./gcc/xgcc -B/home/e0082888/Downloads/build/./gcc/ -B/home/e0082888/powerpc-eabi/pow checking for C compiler default output file name... configure: error: in `/home/e0082888/Downloads/build/powerpc-eabi/libada': configure: error: C compiler cannot create executables See `config.log' for more details. make[1]: *** [configure-target-libada] Error 1 make[1]: Leaving directory `/home/e0082888/Downloads/build' make: *** [all] Error 2
