I think there's a problem in the build sequence for toolchains ia64-unknown-linux-gnu; after building binutils it proceeds with glibc-headers (which fails because it needs ia64-unknown-linux-gnu-cpp) instead of with gcc stage 1. Reproducible: Always Steps to Reproduce: 1. crossdev -S -t ia64-unknown-linux-gnu Actual Results: Output: -------------------------------------------------------------------------------- * Host Portage ARCH: amd64 * Target Portage ARCH: ia64 * Target System: ia64-unknown-linux-gnu * Stage: 4 (C/C++ compiler) * binutils: binutils-[stable] * gcc: gcc-[stable] * headers: linux-headers-[stable] * libc: glibc-[stable] * PORTDIR_OVERLAY: /usr/local/portage * PORT_LOGDIR: /var/log/portage * PKGDIR: /usr/portage/packages/cross/ia64-unknown-linux-gnu * PORTAGE_TMPDIR: /var/tmp/cross/ia64-unknown-linux-gnu _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - * Forcing the latest versions of {binutils,gcc}-config/gnuconfig ... [ ok ] * Log: /var/log/portage/cross-ia64-unknown-linux-gnu-binutils.log * Emerging cross-binutils ... [ ok ] * Log: /var/log/portage/cross-ia64-unknown-linux-gnu-linux-headers-quick.log * Emerging cross-linux-headers-quick ... [ ok ] * Log: /var/log/portage/cross-ia64-unknown-linux-gnu-glibc-headers.log * Emerging cross-glibc-headers ... * glibc failed :( * If you file a bug, please attach the following logfiles: * /var/log/portage/cross-ia64-unknown-linux-gnu-info.log * /var/log/portage/cross-ia64-unknown-linux-gnu-glibc-headers.log
Created attachment 129471 [details] Log file
you posted the wrong log files ... you should have posted: /var/log/portage/cross-ia64-unknown-linux-gnu-info.log /var/log/portage/cross-ia64-unknown-linux-gnu-glibc-headers.log but you attached: /var/log/portage/cross-ia64-unknown-linux-gnu-linux-headers-quick.log please re-open once you've posted the correct ones
Created attachment 129497 [details] cross-ia64-unknown-linux-gnu-glibc-headers.log
Created attachment 129499 [details] cross-ia64-unknown-linux-gnu-info.log
Requested log files provided. As mentioned earlier, the problem is the apparent absence of ia64-unknown-linux-gnu-cpp, which is not built until gcc stage 1. Looks like a classic chicken-and-the-egg problem: to build the headers you need the compiler, but the compiler apparently needs the headers. From looking inside the crossdev script I can see that ia64 is a special case, which gets a special flag (WITH_DEF_HEADERS) set to "yes".
fixed in cvs