From: tdrueke <tdrueke@gmx.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: what about glibc upgrade (was: Re: [gentoo-user] gcc 4.1 with gentoo 2006.1)
Date: Thu, 31 Aug 2006 20:46:21 +0200 [thread overview]
Message-ID: <1157049981.13259.15.camel@halde.meinedomain.de> (raw)
In-Reply-To: <7573e9640608311138g4d97d533wdaba28395b0d8514@mail.gmail.com>
Sorry, didn't make my point clear.
I already upgraded to gcc-4.1.1 with profile 2006.0
(by ~x86 keyword) with "emerge -e system && emerge -e world".
Switching to 2006.1 now leads to glibc upgrade.
Is it necessary to perform "emerge -e world" again ?
BR
Thomas
On Thu, 2006-08-31 at 11:38 -0700, Richard Fish wrote:
> On 8/31/06, tdrueke <tdrueke@gmx.net> wrote:
> > What about the glibc upgrade from 2.3 to 2.4.
> > Does the same concerning "emerge -e world" apply here
> > (e.g. it is recommended to do it) ?
> >
> > Or is it a more relaxed situation and simply emerging glibc 2.4 is
> > enough ?
>
> When you emerge -e world for the gcc upgrade, you will get the new glibc.
>
> -Richard
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-08-31 18:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 22:07 [gentoo-user] gcc 4.1 with gentoo 2006.1 Stefan G. Weichinger
2006-08-30 22:55 ` Stefan G. Weichinger
2006-08-31 15:20 ` Philip Webb
2006-08-31 16:16 ` Dale
2006-08-31 17:48 ` Thomas T. Veldhouse
2006-08-31 18:31 ` what about glibc upgrade (was: Re: [gentoo-user] gcc 4.1 with gentoo 2006.1) tdrueke
2006-08-31 18:38 ` Richard Fish
2006-08-31 18:46 ` tdrueke [this message]
2006-08-31 18:59 ` Richard Fish
2006-08-31 19:08 ` tdrueke
2006-08-31 18:51 ` Hemmann, Volker Armin
2006-08-31 18:52 ` [gentoo-user] gcc 4.1 with gentoo 2006.1 Neil Bothwick
2006-08-31 19:06 ` Thomas T. Veldhouse
2006-08-31 20:41 ` Philip Webb
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=1157049981.13259.15.camel@halde.meinedomain.de \
--to=tdrueke@gmx.net \
--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