public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Bob Young" <BYoung@nucoretech.com>
To: <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] gcc-4.1.1
Date: Wed, 7 Jun 2006 18:50:55 -0700	[thread overview]
Message-ID: <FAEEIJPAOFEMBBLKPMJEOEEPGCAA.BYoung@NuCORETech.com> (raw)
In-Reply-To: <7573e9640606071625i4082dd14p6c66082f503a4ae9@mail.gmail.com>


> On 6/7/06, Roy Wright <royw@cisco.com> wrote:
> > You might want to read:
> >
> > http://forums.gentoo.org/viewtopic.php?t=282474&highlight=
> >
> > which basically recommends:
> >
> >   emerge -s
> >   emerge -s
> >   emerge -e
> >   emerge -e
>
>
> Ugh, this is completely pointless.  A single "emerge -e world" is
> sufficient.
>

Depends on what you consider sufficient. Although what the page recommends
was misquoted, it actually suggests:

emerge -e system
emerge -e system
emerge -e world
emerge -e world

That's probably is a little bit excessive, but the reason for doing the two
emerge -e systems is so that the new tool chain is built with the new tool
chain. At the end of the first emerge -e system you may have a new compiler,
but that new compiler was built with the old compiler. What you actually
want is a gcc-4.1.1 that was built with gcc-4.1.1. You could emerge the
compiler twice before doing the emerge -e system, but the the emerges that
happen before glibc is rebuilt are linked against a glibc that was built
with the old compiler. Same with the rest of the tool chain and libraries.

That being said "emerge -e system" is probably overkill just for a new
toolchain. Updating a subset of all possible toolchain related things and
then following that by a single emerge -e world would probably be sufficient
for most people. This page: http://forums.gentoo.org/viewtopic-t-345229.html
is about doing an install, but it shows how to update a subset of the entire
tool chain. Note that the article does in the end, do a double emerge -e
system, so the the value of updating a toolchain subset is questionable for
the article's purposes.

In short:

emerge gcc-config glibc binutils libstdc++-v3 gcc
emerge gcc-config glibc binutils libstdc++-v3 gcc
emerge -e world

To be clear, in order to make sure absolutely everything is updated and the
libraries that are linked against are also updated prior to use, the two
emerge -e system commands, are the definitive solution. For those who don't
want to spend many extra hours of compile time, in order to gain a 0.5%
increase in performance, the above is offered for consideration.

Regards,
Bob Young


-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2006-06-08  2:01 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ad4496950606070647s5a4bc702m8deeda7dbd590c4a@mail.gmail.com>
2006-06-07 13:53 ` [gentoo-user] gcc-4.1.1 Mohammed Hagag
2006-06-07 14:30   ` Peper
2006-06-07 14:35     ` Julien Cabillot
2006-06-07 14:45   ` Kristian Poul Herkild
2006-06-07 14:56   ` Neil Bothwick
2006-06-07 15:00   ` Bo Ørsted Andresen
2006-06-07 15:25   ` Conneries wearegeeks
2006-06-07 16:04   ` Roy Wright
2006-06-07 17:46     ` Mike Huber
2006-06-07 18:09       ` Daniel da Veiga
2006-06-07 19:27         ` Roy Wright
2006-06-07 19:55           ` Daniel da Veiga
2006-06-07 18:17       ` Evan Klitzke
2006-06-07 23:25     ` Richard Fish
2006-06-08  0:32       ` Evan Klitzke
2006-06-08  4:40         ` Richard Fish
2006-06-08 11:39           ` Mohammed Hagag
2006-06-08  1:50       ` Bob Young [this message]
2006-06-08  2:10         ` Jerry McBride
2006-06-12 21:35           ` Bob Young
2006-06-13  0:09             ` Richard Fish
2006-06-08  4:24         ` Richard Fish
2006-06-08 12:34           ` Bob Young
2006-06-08 13:31             ` Hans-Werner Hilse
2006-06-08 14:00               ` Bob Young
2006-06-08 14:28                 ` Bo Ørsted Andresen
2006-06-08 14:57                   ` Bob Young
2006-06-08 15:27                 ` Toby Cubitt
2006-06-08 18:05             ` Richard Fish
2006-06-09 11:50               ` Vladimir G. Ivanovic
2006-06-09 19:43                 ` Richard Fish
2006-06-16 17:25             ` Thomas T. Veldhouse
2006-06-16 17:50               ` Bob Young
2006-06-16 17:17         ` Thomas T. Veldhouse

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=FAEEIJPAOFEMBBLKPMJEOEEPGCAA.BYoung@NuCORETech.com \
    --to=byoung@nucoretech.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