Alexander Wieder wrote: > I tried to build GCC 4.2 (core and g++) on my linux box (Ubuntu 7.04, > amd64). Except a program-suffix and an install prefix, I used no > configure options. Building failed with the following messages: > > > [...] > > checking for x86_64-unknown-linux-gnu-gcc... /home/alexx/tmp/gcc-build/./gcc/xgcc -B/home/alexx/tmp/gcc-build/./gcc/ -B/home/alexx/local/gcc/x86_64-unknown-linux-gnu/bin/ -B/home/alexx/local/gcc/x86_64-unknown-linux-gnu/lib/ -isystem /home/alexx/local/gcc/x86_64-unknown-linux-gnu/include -isystem /home/alexx/local/gcc/x86_64-unknown-linux-gnu/sys-include -m32 > > checking for C compiler default output file name... a.out > > checking whether the C compiler works... configure: error: cannot run C compiled programs. > > If you meant to cross compile, use `--host'. > > See `config.log' for more details. > > make[1]: *** [configure-target-libmudflap] Error 1 > > make[1]: Leaving directory `/home/alexx/tmp/gcc-build' > > make: *** [all] Error 2 I wonder if you are running into the problem where debian-based distros use the non-standard 64 bit /usr/lib and 32 bit /usr/lib32, whereas the rest of the world uses 64 bit /usr/lib64 and 32 bit /usr/lib. I think this makes it impossible to build a multilib gcc without patches on such systems. You can --disable-multilib and see if that fixes the problem. Brian
