public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andrey Falko" <ma3oxuct@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] A question about emerge --info
Date: Wed, 29 Oct 2008 16:23:30 -0700	[thread overview]
Message-ID: <350fc7cf0810291623j5fb5608rf311cd0d2a371d2a@mail.gmail.com> (raw)
In-Reply-To: <e38d12ff0810291613t6205b80em1294991c930ce1cf@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1623 bytes --]

On Wed, Oct 29, 2008 at 4:13 PM, Andrey Vul <andrey.vul@gmail.com> wrote:

> On Wed, Oct 29, 2008 at 7:09 PM, Andrey Falko <ma3oxuct@gmail.com> wrote:
> >
> >
> > On Wed, Oct 29, 2008 at 3:53 PM, Paul Hartman
> > <paul.hartman+gentoo@gmail.com <paul.hartman%2Bgentoo@gmail.com>> 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:
> >>
> >> Linux-2.6.27-gentoo-r1-x86_64-Intel-R-_Core-TM-2_CPU_6600_@
> _2.40GHz-with-glibc2.2.5
> >> 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.
> >
> 2.6.27 uses glibc? Really?
> I'm asking lkml what's happening.
>
>
> --
> Andrey Vul
>
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
>
>
Well it doesn't use glibc per se, gcc uses the glibc.....however, his uname
-a output does look funky.

Here is mine: System uname: 2.6.24.7 x86_64 Intel(R) Core(TM)2 CPU 6700 @
2.66GHz

Did all underscores make it there by accident? What happens when you do a
plain uname -a?

[-- Attachment #2: Type: text/html, Size: 2336 bytes --]

  reply	other threads:[~2008-10-29 23:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-29 22:53 [gentoo-user] A question about emerge --info Paul Hartman
2008-10-29 23:06 ` Andrey Vul
2008-10-29 23:09 ` Andrey Falko
2008-10-29 23:13   ` Andrey Vul
2008-10-29 23:23     ` Andrey Falko [this message]
2008-10-29 23:32       ` Andrey Vul
2008-10-29 23:41         ` Andrey Vul
2008-10-29 23:51           ` Andrey Vul
2008-10-29 23:57             ` Andrey Falko
2008-10-30  0:03               ` Andrey Vul
2008-10-30  0:15                 ` Andrey Falko
2008-10-30  0:26                   ` Andrey Vul
2008-10-30  2:02                   ` Andrey Vul
2008-10-30 10:37                     ` Geralt
2008-10-30  1:49                 ` Paul Hartman
2008-10-30  0:47             ` Joshua Murphy
2008-10-30  1:30               ` Andrey Vul
2008-10-30  1:31               ` Andrey Vul
2008-10-30 12:26               ` Albert Hopkins
2008-10-30 12:43                 ` Heiko Wundram
2008-10-30 13:44                   ` Albert Hopkins
2008-10-29 23:21   ` Paul Hartman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=350fc7cf0810291623j5fb5608rf311cd0d2a371d2a@mail.gmail.com \
    --to=ma3oxuct@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox