This bugreport might be a bit bloat, but I still add it here, if others get stuck with the same fault (I'm poting the "fix" here aswell) Symptom: Calculating dependencies... done! >>> Verifying ebuild manifests >>> Emerging (1 of 1) sys-libs/glibc-2.7-r2 * glibc-libidn-2.7.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * glibc-ports-2.7.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * glibc-2.7.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * glibc-2.7-patches-1.7.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] >>> Unpacking source... * Checking gcc for __thread support ... [ ok ] * Checking kernel version (>=2.6.9) ... * Checking linux-headers version (>=2.6.9) ... i686-pc-linux-gnu-gcc: no input files [ !! ] * You need linux-headers of at least version 2.6.9 * for NPTL support! * * ERROR: sys-libs/glibc-2.7-r2 failed. * Call stack: * ebuild.sh, line 49: Called src_unpack * environment, line 3155: Called eblit-run 'src_unpack' * environment, line 992: Called eblit-glibc-src_unpack * src_unpack.eblit, line 125: Called toolchain-glibc_src_unpack * src_unpack.eblit, line 61: Called check_nptl_support * src_unpack.eblit, line 46: Called die * The specific snippet of code: * die "linux-headers version too low!" * The die message: * linux-headers version too low! * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.7-r2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.7-r2/temp/environment'. * Even thought sys-kernel/linux-headers-2.6.27-r2 is installed. After some fidling and reading the ebuild sources, I traced down the problem. My CPP setting; due to bug #206240, is was set to CPP="${CHOST}-gcc -E" Setting it back to CPP=${CHOST}-cpp solves the issue. Reproducible: Always Steps to Reproduce: 1. emerge glibc-2.7 with CPP set to gcc -E
I think you've missed the fact that the bug you've mentioned was closed as invalid, as in: 'self-harm'.
