On Wed, Oct 29, 2008 at 6:09 PM, Andrey Falko <[EMAIL PROTECTED]> wrote: > > > On Wed, Oct 29, 2008 at 3:53 PM, Paul Hartman > <[EMAIL PROTECTED]> wrote: >> >> I've always been curious about something in emerge --info's output: >> >> $ emerge --info >> Portage 2.2_rc12 (default/linux/amd64/2008.0/desktop, gcc-4.3.2, >> glibc-2.8_p20080602-r0, 2.6.27-gentoo-r1 x86_64) >> ================================================================= >> System uname: >> >> [EMAIL PROTECTED] >> Timestamp of tree: Tue, 28 Oct 2008 00:31:02 +0000 >> >> Why does it show the glibc-2.8 on the second line but glibc2.2.5 on the >> fifth? >> >> Thanks, >> Paul >> > > My best guess is that your kernel was compiled by a toolchain that was > running on glibc2.2.5 > > See what happens if you recompile the kernel under the newer toolchain.
By toolchain do you mean gcc/binutils? Both have been built since I've had glibc 2.8 installed. When I build my kernel I just "make all" (after configuring, of course). I've never even had glibc2.2.5 on this computer. The earliest was 2.5 and I've been using 2.8 since June. That's why the message confuses me. "uname -a" does not actually mention anything about glibc, but emerge --info is getting it from somewhere. I haven't tried to look into the depths of emerge sources yet to figure out exactly where it's getting that info. Thanks, Paul
