From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.50) id 1Ef9Gj-0007vp-Mc for garchives@archives.gentoo.org; Thu, 24 Nov 2005 05:03:38 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id jAO528Xa018170; Thu, 24 Nov 2005 05:02:08 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id jAO4wEeP008427 for ; Thu, 24 Nov 2005 04:58:14 GMT Received: from 82-41-57-20.cable.ubr08.edin.blueyonder.co.uk ([82.41.57.20] helo=snowdrop.home) by smtp.gentoo.org with esmtpa (Exim 4.43) id 1Ef9BW-0001kR-Bk for gentoo-user@lists.gentoo.org; Thu, 24 Nov 2005 04:58:14 +0000 Received: from localhost.home ([127.0.0.1] helo=snowdrop.home) by snowdrop.home with esmtp (Exim 4.54) id 1Ef9BT-0008IW-RU for gentoo-user@lists.gentoo.org; Thu, 24 Nov 2005 04:58:11 +0000 Date: Thu, 24 Nov 2005 04:58:07 +0000 From: Ciaran McCreesh To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: changing CHOST in stage3 Message-ID: <20051124045807.0cf15319@snowdrop.home> In-Reply-To: References: <20051122131727.0ce8e6ad@snowdrop.home> X-Mailer: Sylpheed-Claws 1.9.100 (GTK+ 2.6.10; i686-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_=d06V/EuVg5fW4TnJCi=KaK"; protocol="application/pgp-signature"; micalg=PGP-SHA1 X-Archives-Salt: b1050585-87a2-44f6-b475-34e68f89585f X-Archives-Hash: 98fdbbe4ee33edb6226aea5244e088b3 --Sig_=d06V/EuVg5fW4TnJCi=KaK Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Wed, 23 Nov 2005 15:34:27 -0500 Allan Gottlieb wrote: | At Tue, 22 Nov 2005 13:17:27 +0000 Ciaran McCreesh | wrote: | > The only way you can safely change CHOST is by making new stages | > through catalyst. There're various scripts which *sometimes* fix | > your system after a CHOST change, but they're not reliable... |=20 | Does this mean that, if one needs a CHOST value not represented in any | of the current stage3 tar files, your recommendation would be to begin | with a stage1? Nope. You need a stage3 to build a stage1 with a new CHOST. --=20 Ciaran McCreesh : Gentoo Developer (Look! Shiny things!) Mail : ciaranm at gentoo.org Web : http://dev.gentoo.org/~ciaranm --Sig_=d06V/EuVg5fW4TnJCi=KaK Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDhUhj96zL6DUtXhERAvFjAKCZNMCyaantHXpQlGt9RvTFCKnjhgCfSRtF 454SIPjsNawT7s+4WRGKIwE= =OFO2 -----END PGP SIGNATURE----- --Sig_=d06V/EuVg5fW4TnJCi=KaK-- -- gentoo-user@gentoo.org mailing list