From: tdrueke <tdrueke@gmx.net>
To: gentoo-user@lists.gentoo.org
Subject: what about glibc upgrade (was: Re: [gentoo-user] gcc 4.1 with gentoo 2006.1)
Date: Thu, 31 Aug 2006 20:31:40 +0200 [thread overview]
Message-ID: <1157049100.13259.11.camel@halde.meinedomain.de> (raw)
In-Reply-To: <44F720F4.3010906@veldy.net>
Sorry for capturing the thread. :)
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 ?
BR
Thomas
On Thu, 2006-08-31 at 12:48 -0500, Thomas T. Veldhouse wrote:
> Dale wrote:
> > Since this is a major upgrade you may want to reconsider. So I guess it
> > depends on how much risk you want to take with it. If anything, at
> > least do a emerge -e system. That should get you booted even if the GUI
> > fails for some reason.
> >
> > Dale
> > :-) :-)
> >
>
>
> As has always been the case, C++ applications are probably the most
> likely to be affected by ABI changes. So, if you run KDE or Qt apps,
> then it is probably a very good idea to rebuild world.
>
> Tom
>
>
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-08-31 18:35 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 ` tdrueke [this message]
2006-08-31 18:38 ` what about glibc upgrade (was: Re: [gentoo-user] gcc 4.1 with gentoo 2006.1) Richard Fish
2006-08-31 18:46 ` tdrueke
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=1157049100.13259.11.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