From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: changing CHOST in stage3
Date: Thu, 24 Nov 2005 19:55:03 +0000 [thread overview]
Message-ID: <20051124195503.4b3ed3b0@snowdrop.home> (raw)
In-Reply-To: <yu9k6eyos25.fsf@nyu.edu>
[-- Attachment #1: Type: text/plain, Size: 825 bytes --]
On Thu, 24 Nov 2005 12:48:34 -0500 Allan Gottlieb <gottlieb@nyu.edu>
wrote:
| It surprises me that release engineering starts with a stage1 to get a
| stage3 and then we use this stage3 to build a stage1. I mention this
| only out of curiosity; there is a stage3 with my desired CHOST and I
| expect to do all future installs starting with stage3 (I formerly used
| stage1).
Well... You need a reasonably complete system to build a toolchain,
hence the stage 3 seed. Building a toolchain with a different CHOST is
pretty close to cross-compiling, so the only way you can do it safely
is to start from scratch, hence building up from a stage 1.
--
Ciaran McCreesh : Gentoo Developer (Supreme Lord Gerbil Wrangler)
Mail : ciaranm at gentoo.org
Web : http://dev.gentoo.org/~ciaranm
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-11-24 20:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 2:08 changing CHOST in stage3 (was : [gentoo-user] default stage3) Matthew Cline
2005-11-22 6:06 ` Alexander Skwar
2005-11-22 11:33 ` Neil Bothwick
2005-11-22 22:11 ` Matthew Cline
2005-11-22 23:16 ` Matthias Langer
2005-11-23 0:52 ` Richard Fish
2005-11-23 5:55 ` Richard Fish
2005-11-23 5:57 ` Alexander Skwar
2005-11-24 1:24 ` Robin
2005-11-24 1:42 ` W.Kenworthy
2005-11-22 13:17 ` Ciaran McCreesh
2005-11-23 20:34 ` [gentoo-user] Re: changing CHOST in stage3 Allan Gottlieb
2005-11-24 4:58 ` Ciaran McCreesh
2005-11-24 17:48 ` Allan Gottlieb
2005-11-24 19:55 ` Ciaran McCreesh [this message]
2005-11-25 3:30 ` Allan Gottlieb
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=20051124195503.4b3ed3b0@snowdrop.home \
--to=ciaranm@gentoo.org \
--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