cd /TMP/build-gcc-svn20060906-powerpc64 /TMP/gcc-svn20060906/configure --target=powerpc64-linux --prefix=/usr/local/DIR/gcc-powerpc64-svn20060906 --enable-languages=c --with-as=/usr/local/bin/powerpc64-linux-as --with-ld=/usr/local/bin/powerpc64-linux-ld --disable-shared --enable-threads=single --disable-multilib make results in: <-- snip --> ... make[2]: Leaving directory `/TMP/build-gcc-svn20060906-powerpc64/gcc' Checking multilib configuration for libmudflap... mkdir -p -- powerpc64-linux/libmudflap Configuring in powerpc64-linux/libmudflap configure: creating cache ./config.cache checking build system type... i686-pc-linux-gnu checking host system type... powerpc64-unknown-linux-gnu checking target system type... powerpc64-unknown-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for powerpc64-linux-strip... powerpc64-linux-strip checking for --enable-version-specific-runtime-libs... no checking whether to enable maintainer-specific portions of Makefiles... no checking for powerpc64-linux-gcc... /TMP/build-gcc-svn20060906-powerpc64/./gcc/x gcc -B/TMP/build-gcc-svn20060906-powerpc64/./gcc/ -B/usr/local/DIR/gcc-powerpc64 -svn20060906/powerpc64-linux/bin/ -B/usr/local/DIR/gcc-powerpc64-svn20060906/pow erpc64-linux/lib/ -isystem /usr/local/DIR/gcc-powerpc64-svn20060906/powerpc64-li nux/include -isystem /usr/local/DIR/gcc-powerpc64-svn20060906/powerpc64-linux/sy s-include checking for C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details. make[1]: *** [configure-target-libmudflap] Error 1 make[1]: Leaving directory `/TMP/build-gcc-svn20060906-powerpc64' make: *** [all] Error 2 <-- snip --> I can workaround this issue with "--disable-libmudflap --disable-libssp".
Created attachment 12197 [details] configure log
Created attachment 12198 [details] make log
Created attachment 12199 [details] powerpc64-linux/libmudflap/config.log
Note: "checking host system type... powerpc64-unknown-linux-gnu" is obviously wrong
Subject: Re: [4.0/4.1/4.2 regression] building a cross compiler with --disable-multilib fails On Wed, 2006-09-06 at 14:19 +0000, bunk at stusta dot de wrote: > > ------- Comment #4 from bunk at stusta dot de 2006-09-06 14:19 ------- > Note: > "checking host system type... powerpc64-unknown-linux-gnu" is obviously wrong No it is not. -- Pinski
/usr/local/DIR/gcc-powerpc64-svn20060906/powerpc64-linux/sys-include -O2 -g -O2 conftest.c >&5 /usr/local/bin/powerpc64-linux-ld: crt1.o: No such file: No such file or directory collect2: ld returned 1 exit status That means you don't have binutils/glibc installed correctly. And this is not a regression anyways.
I don't have a glibc for this target. But this might be where my problems are coming from: I am able to compile gcc 4.1.1 for at about a dozen targets without having any libc for these targets present. And the resulting compilers work fine for my purposes (cross-compiling Linux kernels). But the configure options I had to figure out for doing this seem to indicate that this is a working but not documented setup. It seems sending a bug report for part of this wasn't the right solution. Is there a good reason why gcc can't officially support being built without a libc by either figuring out that there's no libc itself or by offering some kind of --i-do-not-have-a-libc option to configure?
(In reply to comment #7) > Is there a good reason why gcc can't officially support being built without a > libc by either figuring out that there's no libc itself or by offering some > kind of --i-do-not-have-a-libc option to configure? Yes because you are configuring wrong in the first place. Try looking at what crosstool does for how to build a cross compiler. http://kegel.com/crosstool/
You should disable libmudflap and libssp (in newer gcc's) if you want to build a cross compiler to start stage1.