At first, I ran into the same problem described in <a href="/show_bug.cgi?id=84481">#84481</a>, but it turned out that (as for the original bug reporter) the installed x86 libtool was incompatible. I fixed that, and then crossdev proceeded to build gcc-stage1 and linux-headers without incident. It bombs out of building glibc, however. Log files are attached. Reproducible: Always Steps to Reproduce: 1. 2. 3. Portage 2.0.51.19 (default-linux/x86/2004.0, gcc-3.3.5, glibc-2.3.4.20040808-r1, 2.6.10 i686) ================================================================= System uname: 2.6.10 i686 AMD Athlon(tm) processor Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4 [2.3.4 (#1, Jan 25 2005, 14:34:29)] distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.3 [enabled] dev-lang/python: 2.3.4 sys-devel/autoconf: 2.59-r5 sys-devel/automake: 1.8.5-r1 sys-devel/binutils: 2.15.92.0.2-r7 sys-devel/libtool: 1.4.3-r3, 1.5.2-r7 virtual/os-headers: 2.4.21-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=i686 -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/alias /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=i686 -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distcc distlocks sandbox sfperms" GENTOO_MIRRORS="ftp://mirrors.tds.net/gentoo http://csociety-ftp.ecn.purdue.edu/pub/gentoo/ http://mirror.tucdemonic.org/gentoo/ ftp://gentoo.ccccom.com" MAKEOPTS="-j4" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 3dnow X apm arts avi berkdb bitmap-fonts cdr crypt cups curl emboss encode faad flac font-server foomaticdb fortran gd gdbm gif gpm gtk gtk2 imlib ipv6 javascript jpeg kde libg++ libwww mad maildir mikmod motif mp3 mpeg mysql ncurses nls oggvorbis opengl oss pam pdflib perl png postgres python qt quicktime readline samba sdl session slang spell ssl svga tcltk tcpd tetex tiff truetype truetype-fonts type1-fonts xml2 xmms xv zlib" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS
Created attachment 54206 [details] cross-powerpc-unknown-linux-gnu-glibc.log
Created attachment 54207 [details] cross-powerpc-unknown-linux-gnu-info.log
Created attachment 54209 [details] config.log Attachment #<a href="/attachment.cgi?id=54206">54206</a> says to refer to this file for more details.
Updating virtual/os-headers from 2.4.21-r1 to 2.6.8.1-r2 made no difference, FWIW. About the only native-toolchain element not upgraded yet is gcc. I'm trying to build gcc 3.4.3 as a cross-compiler for PowerPC because emerge world on my Power Mac G3 decided to grab it (the stage3 tarball came with gcc-3.4.3-r1 and emerge world is building gcc-3.4.3-r3, while the gcc-3.3.5-r1 that's currently installed on my Athlon box is the newest stable version for x86. I ordinarily wouldn't bother building PPC glibc because I just want the C and C++ compilers to be available to distcc, but the C++ compiler apparently can't be built without glibc.
you're running stable x86, chances are your host toolchain is screwing things up
My host toolchain meets all of the minimums given at http://dev.gentoo.org/~vapier/CROSS-COMPILE-HOWTO: glibc-2.3.4.20040808-r1, binutils-2.15.92.0.2-r7, gcc-3.3.5-r1, linux26-headers-2.6.8.1-r2. If there is some additional dependency that isn't specified on that page, perhaps it should be updated so that people won't file bugs here that end up getting tagged WONTFIX. I've thrown together another x86 Gentoo box with the instructions given at http://forums.gentoo.org/viewtopic-t-189250-postdays-0-postorder-asc-start-0.html. It's using binutils-2.15.92.0.2-r7 (same as above), gcc-3.4.3.20050110-r1 (updated), glibc-2.3.4.20050125-r1 (updated), and linux26-headers-2.6.8.1-r2 (same as above). Maybe that'll make a difference.
eh, i didnt really read your config.log, i just assumed you did it wrong :p
that said, your config.log shows that you're using the wrong CFLAGS: configure:2672: powerpc-unknown-linux-gnu-gcc -c -O2 -march=i686 -finline-limit=2000 -O2 conftest.c >&5 cc1: error: invalid option `arch=i686'
configure:2672: powerpc-unknown-linux-gnu-gcc -c -O2 -march=i686 -finline-limit=2000 -O2 conftest.c >&5 cc1: error: invalid option `arch=i686' I didn't notice that. It does seem bizarre that it would try to apply an x86 optimization to a PowerPC build. I'm trying the build again on the first system with CFLAGS and CXXFLAGS unset to see if that'll allow it to build. (tail -f /var/log/portage/cross-powerpc-unknown-linux-gnu-glibc.log shows some compiling activity.) The crossdev-0.9.5 ebuild on the second system failed at the same point, so I'm doing the same thing with it: build stage 2 (glibc) with CFLAGS & CXXFLAGS unset, then stage 3 with the usual CFLAGS & CXXFLAGS. I'll post an update when they're done.
crossdev just uses portage which defaults to the CFLAGS in your /etc/make.conf ;) you should `export CFLAGS="-O2 -pipe"` when running crossdev
