public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Stéphane Guedon" <stephane@22decembre.eu>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Upgrading gcc: both 4.4 and 4.5 needed?
Date: Wed, 16 Nov 2011 08:11:16 +0100	[thread overview]
Message-ID: <201111160811.17331.stephane@22decembre.eu> (raw)
In-Reply-To: <CAA2qdGXF9pfpsy7FvpPJtXvcDB0WJ+xD0SAURLLxsbm713FWpw@mail.gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 1597 bytes --]

On Wednesday 16 November 2011 02:07:12 Pandu Poluan wrote:
> On Nov 16, 2011 8:00 AM, "Nikos Chantziaras" <realnc@arcor.de> wrote:
> > On 11/15/2011 08:58 PM, Jarry wrote:
> >> Hi,
> >> today I upgraded gcc from 4.4.5 to the last stable version
> >> 4.5.3-r1.
> >> [...]
> >> 
> >> But at the and I noticed gcc 4.4 has not been unmerged
> >> and my "world" file is somehow larger. To my surprise,
> >> it contains these lines:
> >> 
> >> sys-devel/gcc
> >> sys-devel/gcc:4.4
> >> 
> >> I did full backup before, so I compared world-file before
> >> and after gcc-upgrade just to find out, these two lines
> >> have been really inserted now, during gcc-upgrade. And my
> >> question is: what does it mean? Does my system need now
> >> both gcc 4.4 and 4.5? Why is actually gcc in world-file,
> >> when it is part of system?
> > 
> > The old GCC version does not get removed.  This is a good thing just in
> 
> case the new one doesn't work for some reason.
> 
> > If it works OK, you can manually unmerge the old version:
> >  emerge -aC gcc:4.4
> > 
> > Before doing that, however, make sure the new one has been activated with
> 
> gcc-config and verify that it works by building some random package.
> 
> 
> And if you're adventurous, add USE "graphite", reemerge gcc, and reemerge
> world :)
> 
> Rgds,

what does "graphite" add ?

thanks

-- 
Stéphane Guedon
page web : http://www.22decembre.eu/
carte de visite : http://www.22decembre.eu/downloads/Stephane-Guedon.vcf
clé publique gpg : http://www.22decembre.eu/downloads/Stephane-Guedon.asc

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 316 bytes --]

  reply	other threads:[~2011-11-16  7:12 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-15 18:58 [gentoo-user] Upgrading gcc: both 4.4 and 4.5 needed? Jarry
2011-11-15 19:36 ` Andrey Moshbear
2011-11-15 19:48   ` Jarry
2011-11-15 20:16     ` Dale
2011-11-16 13:32     ` Alex Schuster
2011-11-16 19:26       ` Dale
2011-11-16 19:34         ` Mark Knecht
2011-11-16  0:54 ` [gentoo-user] " Nikos Chantziaras
2011-11-16  1:07   ` Pandu Poluan
2011-11-16  7:11     ` Stéphane Guedon [this message]
2011-11-16  7:20       ` Andrey Moshbear
2011-11-16  7:21       ` Michael Mol
2011-11-16 13:58         ` Pandu Poluan
2011-11-18 15:39           ` Fredric Johansson
2011-11-18 16:35             ` Pandu Poluan
2011-11-18 16:50               ` Pandu Poluan
2011-11-16  8:29       ` Pandu Poluan
2011-11-16 13:30         ` Willie Wong
2011-11-16 13:51           ` Albert W. Hopkins
2011-11-17 19:41           ` James
2011-11-18 14:24             ` Willie Wong
2011-11-18 15:05               ` Pandu Poluan
2011-11-18 15:24               ` Michael Mol

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=201111160811.17331.stephane@22decembre.eu \
    --to=stephane@22decembre.eu \
    --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