From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Gcc 4.3.4 ---> 4.4.1
Date: Sat, 15 Aug 2009 17:50:29 +0200 [thread overview]
Message-ID: <200908151750.29503.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <20090815003356.GA21363@crowfix.com>
On Saturday 15 August 2009 02:33:56 felix@crowfix.com wrote:
> This being 4.3.4 to 4.1.1 looks like a major version change according
> to the upgrade guide. It doesn't mention what a switch manual takes,
> but it does list a whole series of steps such as remerging system and
> world without saying exactly when they or how much are necessary. I'd
> just as soon not do that unless necessary, but I'd much more regret
> not doing it if I should have.
All you need to do for this gcc-config is select the new compiler for the
system, but only if you choose to.
There are no other steps. If a system rebuild is necessary, the upgrade guide
will say so in terms that make for no confusion, and the ebuild elog will say
the same. They do not, so there is no need.
Look, the amount of confusion in gentoo-land about gcc upgrades defies belief.
The upgrade guide explicitly says it is talking about going from a named
version X to another named version Y, and somehow vast numbers of people morph
this into somehow meaning that it must always be done. This is not true.
It only needs to be done when the compiler introduces ABI changes that make
new object code incompatible with old object code that the new code intends to
use. And it is always well-publicised when this happens (it couldn't be any
other way, the dev's reputations depends on them doing exactly that.)
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2009-08-15 15:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 23:17 [gentoo-user] Gcc 4.3.4 ---> 4.4.1 felix
2009-08-14 23:29 ` [gentoo-user] " walt
2009-08-15 0:33 ` felix
2009-08-15 0:43 ` Nikos Chantziaras
2009-08-15 16:48 ` Mark Knecht
2009-08-15 16:59 ` Nikos Chantziaras
2009-08-15 17:07 ` 7v5w7go9ub0o
2009-08-15 17:39 ` Nikos Chantziaras
2009-08-15 18:35 ` 7v5w7go9ub0o
2009-08-15 18:52 ` Nikos Chantziaras
2009-08-15 18:57 ` Nikos Chantziaras
2009-08-15 15:50 ` Alan McKinnon [this message]
2009-08-15 16:42 ` Mark Knecht
2009-08-15 16:49 ` Nikos Chantziaras
2009-08-15 17:10 ` Mark Knecht
2009-08-15 17:06 ` Dirk Heinrichs
2009-08-15 17:18 ` Mark Knecht
2009-08-15 17:28 ` Alan McKinnon
2009-08-15 17:24 ` Nikos Chantziaras
2009-08-15 17:37 ` Dirk Heinrichs
2009-08-15 17:40 ` Nikos Chantziaras
2009-08-16 12:43 ` Alan McKinnon
2009-08-15 17:25 ` Alan McKinnon
2009-08-15 17:39 ` Dirk Heinrichs
2009-08-15 17:17 ` Alan McKinnon
2009-08-15 7:22 ` [gentoo-user] " Neil Bothwick
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=200908151750.29503.alan.mckinnon@gmail.com \
--to=alan.mckinnon@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