The changes since gcc-4.2 result in no longer being able to setup a cross-toolchain. Reproducible: Always Steps to Reproduce: 1. Start with an up-to-date ~amd64 system 2. crossdev --target i686-pc-linux-gnu 3. crossdev --target powerpc-unknown-linux-gnu 4. crossdev --target i586-gentoo-linux-uclibc 5. etc. Actual Results: In each case, cross-binutils will compile fine, but the first pass of cross-gcc will fail. Expected Results: Several working cross-toolchains that I can use with distccd
Created attachment 158045 [details] /var/log/portage/cross-i686-pc-linux-gnu-info.log
Created attachment 158047 [details] /var/log/portage/cross-i686-pc-linux-gnu-gcc-stage1.log
*** This bug has been marked as a duplicate of bug 227065 ***
(In reply to comment #3) Thank you for taking a look at this so quickly. I just upgraded from crossdev-0.9.18-r8 to -r9, and here are the results : i686-pc-linux-gnu now completes --stage4 without errors, but it seems that compiling the c++ compiler was skipped. "i686-pc-linux-gnu-gcc -v" confirmed this. I ran a second pass with --ex-gcc, and now I have c/c++/fortran support, so I am happy.
Created attachment 158165 [details] /var/log/portage/cross-i686-pc-linux-gnu-gcc-stage2.log
However, the other 2 targets I wanted (powerpc-unknown-linux-gnu and i586-gentoo-linux-uclibc) failed with errors on their libc-headers.
Created attachment 158167 [details] /var/log/portage/cross-powerpc-unknown-linux-gnu-glibc-headers.log
Created attachment 158169 [details] /var/log/portage/cross-i586-gentoo-linux-uclibc-uclibc-headers.log
this isnt a mondo bug to dump every random cross-compile issue you hit
(In reply to comment #9) I'm sorry about that. I didn't realize how involved this problem would be. Back when I was running gcc-4.2.3, crossdev worked flawlessly on those 3 targets. Upon upgrading to gcc-4.3.0/4.3.1, Pandora's box is now opened :)
