public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matthias Langer <mlangc@gmx.at>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: default stage3
Date: Tue, 22 Nov 2005 00:28:26 +0100	[thread overview]
Message-ID: <1132615706.10257.5.camel@sputnik886.ruz-net> (raw)
In-Reply-To: <64e8d2f20511211401l5209d32dy151aa8749ab81563@mail.gmail.com>

On Mon, 2005-11-21 at 17:01 -0500, Ryan Sims wrote:
> > I installed gentoo on a dual Opteron box this weekend, I've always done
> > stage1 installs, but this time decided to try the recommeded stage3 method.
> > I understand the concept of doing an "emerge -e world" in order to get the
> > optimization of a stage1 install, and I've done this ( one time ) on the
> > install I just completed. Can sombody explain why it's necessary/desirable
> > to do this *twice*?
> >
> > What real difference does the second execution really make?
> >
> 
> As I understand it, the first time you recompile new toolchain with
> your old toolchain, and then the 2nd time you're recompiling the
> toolchain with the new toolchain, with the idea that the new toolchain
> will compile/assemble/link/etc everything in a different way than the
> old toolchain.
> 
> Please correct if I'm wrong.

I would suggest 'emerge -uD gcc && emerge -e world'; This should
recompile the new toolchain with the new toolchain and be considerably
faster.

Matthias

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-11-21 23:34 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-21 12:33 default stage3 (was : [gentoo-user] Is Gentoo still on the right path?) Steve B
2005-11-21 12:57 ` Matthias Langer
2005-11-21 13:09   ` Matthias Langer
2005-11-21 12:57 ` Neil Bothwick
2005-11-21 13:13 ` Hemmann, Volker Armin
2005-11-21 15:17   ` Holly Bostick
2005-11-21 18:19     ` Daniel da Veiga
2005-11-21 22:33       ` Holly Bostick
2005-11-21 23:36         ` Anthony Roy
2005-11-22  7:49         ` Philip Webb
2005-11-22  9:24         ` Neil Bothwick
2005-11-22 11:22           ` Robin
2005-11-22 14:07             ` Daniel da Veiga
2005-11-22 17:24           ` Manuel McLure
2005-11-22 23:19             ` William Kenworthy
2005-11-23  0:11               ` Manuel McLure
2005-11-22 23:34             ` Neil Bothwick
2005-11-22  0:09     ` George Garvey
2005-11-22  0:17       ` Manuel McLure
2005-11-22  0:40       ` Holly Bostick
2005-11-22  2:06         ` W.Kenworthy
2005-11-22 11:32         ` Neil Bothwick
2005-11-21 19:20   ` kashani
2005-11-21 20:39     ` John J. Foster
2005-11-21 20:47       ` Jason Dodson
2005-11-21 21:38         ` kashani
2005-11-21 22:10           ` Steven Susbauer
2005-11-21 22:27             ` Manuel McLure
2005-11-22 18:26     ` Hemmann, Volker Armin
2005-11-22 18:44       ` Nagatoro
2005-11-22 20:34         ` Daniel da Veiga
2005-11-22 19:52       ` Billy Holmes
2005-11-22 21:44       ` kashani
2005-11-21 20:15   ` [gentoo-user] Re: default stage3 Allan Gottlieb
2005-11-21 20:50     ` Bob Young
2005-11-21 22:01       ` Ryan Sims
2005-11-21 23:28         ` Matthias Langer [this message]
2005-11-22  9:17           ` Neil Bothwick
2005-11-22 17:03             ` Richard Fish
2005-11-22 18:03             ` Matthias Langer

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=1132615706.10257.5.camel@sputnik886.ruz-net \
    --to=mlangc@gmx.at \
    --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