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.60) (envelope-from ) id 1GJRvW-0005DQ-Bw for garchives@archives.gentoo.org; Sat, 02 Sep 2006 09:36:34 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.6) with SMTP id k829ZcCH018934; Sat, 2 Sep 2006 09:35:38 GMT Received: from shuttle.zlin.dk (port78.ds1-abs.adsl.cybercity.dk [212.242.227.17]) by robin.gentoo.org (8.13.8/8.13.6) with ESMTP id k829V5MD007825 for ; Sat, 2 Sep 2006 09:31:05 GMT Received: from BA.zlin.dk (unknown [10.0.0.3]) by shuttle.zlin.dk (Postfix) with ESMTP id F1E6730037 for ; Sat, 2 Sep 2006 11:31:04 +0200 (CEST) From: Bo =?iso-8859-1?q?=D8rsted_Andresen?= To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] /etc/make.conf: changing CHOST on same system Date: Sat, 2 Sep 2006 11:30:55 +0200 User-Agent: KMail/1.9.4 References: <20060902.064253.74744032.Meino.Cramer@gmx.de> <7573e9640609012238n5133a484pffe54568ecfab756@mail.gmail.com> <20060902.105839.74745199.Meino.Cramer@gmx.de> In-Reply-To: <20060902.105839.74745199.Meino.Cramer@gmx.de> 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="nextPart1489424.y0tzADeSGT"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200609021130.59257.bo.andresen@zlin.dk> X-Archives-Salt: 1967fc0a-daca-4e3a-9fa8-4cd1ae8033a6 X-Archives-Hash: a4ca6b0263a9768a258f763d65728369 --nextPart1489424.y0tzADeSGT Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday 02 September 2006 10:58, Meino Christian Cramer wrote: > So, is it correct / necessary in my case to do the following for > =A0upgrading to gcc-4.1: > > =A0Correct the CHOST fault > =A0emerge -e world > =A0emerge glibc > =A0emerge -e world > =A0emerge gcc > =A0emerge -e world =2E..?. I guess you didn't follow this list too carefully the last couple of days..= =2E=20 Anyway, no you shouldn't emerge -e world more than once! 1. Correct the CHOST in make.conf 2. Make sure the nptl and nptlonly use flags are enabled. 3. *If* you want to upgrade your profile in the near future this may be a g= ood=20 time to do so. This step is optional. You may have a look at [1] for more=20 info about this. 4. Follow the gcc upgrade guide [2]. =46ollowing the gcc upgrade guide will upgrade glibc and pretty much everet= hing=20 else that isn't quite up to date during the emerge -e world. Make sure that= =20 you follow the "General Upgrade Instructions" carefully though. [1] http://www.gentoo.org/doc/en/gentoo-upgrading.xml [2] http://www.gentoo.org/doc/en/gcc-upgrading.xml =2D-=20 Bo Andresen --nextPart1489424.y0tzADeSGT Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQBE+U9T8/kKEzmwNNoRAlj9AKCMK27hJSQAXGNdDEI7M96Epw2hKACgoGul u3cYUQE/3GzGnfDkRyBJaok= =AVnl -----END PGP SIGNATURE----- --nextPart1489424.y0tzADeSGT-- -- gentoo-user@gentoo.org mailing list