From: Alex Schuster <wonko@wonkology.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gcc upgrade - rebuild everything?
Date: Thu, 21 Oct 2010 22:12:00 +0200 [thread overview]
Message-ID: <201010212212.01454.wonko@wonkology.org> (raw)
In-Reply-To: <AANLkTimoL2OFj9dAw1y+1BbNOX1F8xm7tVV26At=7dgL@mail.gmail.com>
Grant writes:
> I just upgraded from gcc-4.4.3-r2 to gcc-4.4.4-r2 and I'm wondering if
> I really need to rebuild everything as it says in the guide:
>
> http://www.gentoo.org/doc/en/gcc-upgrading.xml
The guide seems to be wrong here. Rebuilding does not harm, and it makes
use of tall the cool new compiler optimizations, but normally it is not
necessary.
> If not, when is it necessary?
Only when the API changes, which happened the last time when gcc went from
3.3 to 3.4, I think.
Wonko
next prev parent reply other threads:[~2010-10-21 21:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 19:58 [gentoo-user] gcc upgrade - rebuild everything? Grant
2010-10-21 20:09 ` Dale
2010-10-21 20:12 ` Alex Schuster [this message]
2010-10-21 20:12 ` Paul Hartman
2010-10-21 21:07 ` Alan McKinnon
2010-10-22 16:31 ` Grant
2010-10-21 21:57 ` [gentoo-user] " Nikos Chantziaras
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=201010212212.01454.wonko@wonkology.org \
--to=wonko@wonkology.org \
--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