public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: default stage3
Date: Tue, 22 Nov 2005 09:17:09 +0000	[thread overview]
Message-ID: <20051122091709.1f85a664@krikkit.digimed.co.uk> (raw)
In-Reply-To: <1132615706.10257.5.camel@sputnik886.ruz-net>

[-- Attachment #1: Type: text/plain, Size: 957 bytes --]

On Tue, 22 Nov 2005 00:28:26 +0100, Matthias Langer wrote:

> > 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.

The first command won't do anything, -D doesn't take account of of USE or
CFLAG changes.

emerge -e system && emerge -e world might be better, but there are scripts
on the forums that recompile just what you need, in the best order, such
as; http://forums.gentoo.org/viewtopic-t-282474.html



-- 
Neil Bothwick

I came, I saw, I had no idea what was going on, I left.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-11-22  9:23 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
2005-11-22  9:17           ` Neil Bothwick [this message]
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=20051122091709.1f85a664@krikkit.digimed.co.uk \
    --to=neil@digimed.co.uk \
    --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