Emerging klibc doesn't detect KERNEL_ARCH- /usr/src/linux/include/asm correctly symlinks to asm-i386 I don't see why this is happening, even after reading the ebuild and trying for myself the "readlink blablbal | sed blablab" command myself from klibc-1.4.13.ebuild's line no. 81.
(In reply to comment #0) > Emerging klibc doesn't detect KERNEL_ARCH- > /usr/src/linux/include/asm correctly symlinks to asm-i386 > > I don't see why this is happening, even after reading the ebuild and trying for > myself the "readlink blablbal | sed blablab" command myself from > klibc-1.4.13.ebuild's line no. 81. > The output of the emerge is: [32;01m* [0m Determining the location of the kernel source code [32;01m* [0m Found kernel source directory: [32;01m* [0m /usr/src/linux [32;01m* [0m Found kernel object directory: [32;01m* [0m /lib/modules/2.6.21-gentoo-r4/build [32;01m* [0m Found sources for kernel version: [32;01m* [0m 2.6.21-gentoo-r4 >>> Unpacking source... >>> Unpacking klibc-1.4.13.tar.bz2 to /var/tmp/portage/dev-libs/klibc-1.4.13/work [32;01m* [0m CTARGET = i686-pc-linux-gnu [31;01m* [0m Your kernel sources are not configured for your chosen arch! [31;01m* [0m (KERNEL_ARCH="", ARCH="i386") !!! ERROR: dev-libs/klibc-1.4.13 failed. Call stack: ebuild.sh, line 1621: Called dyn_unpack ebuild.sh, line 753: Called qa_call 'src_unpack' ebuild.sh, line 44: Called src_unpack klibc-1.4.13.ebuild, line 87: Called die !!! Your kernel sources are not configured for your chosen arch! !!! 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/dev-libs/klibc-1.4.13/temp/build.log'.
Post the output of `emerge --info -v`
Created attachment 128408 [details] emerge --info -v
Attached emrge --info -v.
I got essentially the same error -- x86 vs i386. Workaround: Edit klibc-1.5.ebuild and remove the silly test (why on earth should a script make a wild guess about something, then blow up if the actual installation doesn't match it?). Then run "ebuild klibc-1.5.ebuild manifest" to rebuild all the magic numbers. Emerge should then work jes' fine. This is a very important fix, since uvesafb depends on klib and vesafb-tng won't build correctly with 2.6.23+ kernels.
Nearly the same problem on amd64 with kernel 2.6.24-r1: * Your kernel sources are not configured for your chosen arch! * (KERNEL_ARCH="x86", ARCH="x86_64")
I have the same on x86_64 and 2.6.24+
1.5.7 is in the tree, and fixes this issue.