public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <teendale@vista-express.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gcc 4.1 with gentoo 2006.1
Date: Thu, 31 Aug 2006 11:16:52 -0500	[thread overview]
Message-ID: <44F70B74.20808@vista-express.com> (raw)
In-Reply-To: <20060831152019.GA4801@sympatico.ca>

Philip Webb wrote:
> 060831 Stefan G. Weichinger wrote:
>   
>> I got in via eix-sync that there was a stable gcc-4.1.1.
>> Is it recommended/worth it/useful to recompile my stuff now?
>> Remembering recent threads I assume this leads
>> to some "emerge -e system; emerge -e world" to get the full BANG out of it.
>>     
>
> I updated to 4.1.1 some time ago & have been recompiling packages
> only when there's a newer version; others remain compiled by 3.4.5 or 3.3.6 .
> It doesn't seem to break anything.  I never do 'emerge world' anyway.
>
> HTH FWIW ...
>
>   

But according to the guide and to some threads here, it is highly
advised to do the emerge -e system and a emerge -e world as in the
guide.  It !currently! says this:

> 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.
> However, some GCC upgrades break binary compatibility; in such cases a
> rebuild of the affected packages (or even whole toolchain and system)
> might be required.


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
:-)  :-)
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-08-31 16:23 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 [this message]
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
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=44F70B74.20808@vista-express.com \
    --to=teendale@vista-express.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