public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gcc upgrade - rebuild everything?
Date: Thu, 21 Oct 2010 15:12:18 -0500	[thread overview]
Message-ID: <AANLkTimxm6X5TKBJn6rgdsyvD8av3z_3o6MAQvdF6-cJ@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimoL2OFj9dAw1y+1BbNOX1F8xm7tVV26At=7dgL@mail.gmail.com>

On Thu, Oct 21, 2010 at 2:58 PM, Grant <emailgrant@gmail.com> wrote:
> 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
>
> If not, when is it necessary?

As that guide says:

"Generally speaking, upgrades to bug fix releases, like from 3.3.5 to
3.3.6, should be quite safe -- just emerge new version, switch your
system to use it and rebuild the only affected package, libtool."

The "General Upgrade Instructions" are more for major version changes.
I don't think 4.4.3 to 4.4.4 is considered an upgrade in this sense,
just a minor update.

I think even on larger upgrade, like 4.3 to 4.4, it's only necessary
to rebuild everything if libstdc++.so's major version number has
changed. @preserved-rebuild will hopefully give some assistance in
that case anyway (if you're using a version of portage that has it).



  parent reply	other threads:[~2010-10-21 21:10 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
2010-10-21 20:12 ` Paul Hartman [this message]
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=AANLkTimxm6X5TKBJn6rgdsyvD8av3z_3o6MAQvdF6-cJ@mail.gmail.com \
    --to=paul.hartman+gentoo@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