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.54) id 1F2BO1-0007yJ-S4 for garchives@archives.gentoo.org; Thu, 26 Jan 2006 17:58:22 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id k0QHvc9r025479; Thu, 26 Jan 2006 17:57:38 GMT Received: from gw.open-hosting.net (gw.open-hosting.net [65.64.29.89]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id k0QHsuXq004337 for ; Thu, 26 Jan 2006 17:54:57 GMT Received: from speedy.apps4med.net ([66.139.177.227]) by gw.open-hosting.net (8.13.4/8.13.3) with ESMTP id k0QHsleA012883 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 26 Jan 2006 11:54:52 -0600 Message-Id: <200601261754.k0QHsleA012883@gw.open-hosting.net> From: MIkey Subject: [gentoo-dev] Re: Re: Re: bootstrapping since gcc 3.4 is stable To: gentoo-dev@lists.gentoo.org Date: Thu, 26 Jan 2006 11:52:40 -0600 References: <1138284761.10589.54.camel@cgianelloni.nuvox.net> <200601260940.15770.mikey@badpenguins.com> <43D8FA31.2030300@gentoo.org> <200601261718.k0QHHup1012542@gw.open-hosting.net> <43D9097E.7010001@gentoo.org> User-Agent: KNode/0.10 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on gw.open-hosting.net X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham version=3.0.4-gr0 X-Spam-Checker-Version: SpamAssassin 3.0.4-gr0 (2005-06-05) on gw.open-hosting.net Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by robin.gentoo.org id k0QHvcBO025479 X-Archives-Salt: ec84b1f6-42f0-4b44-a752-b8a554537c34 X-Archives-Hash: eb8ab093b1fd00e711348cd54f17d594 Jan Kundr=E1t wrote: > Have you noticed that I'm the reporter of this bug? Just FYI, bug > *wasn't* in the guide but in the underlying eclass/gcc-config causing > automatic switch to newly installed GCC during pkg_postinst. Just by a > coincidence the eclass was updated shortly after gcc/3.4 stabilisation. A bug, again, that the stage1 installation method was immune to, which is the topic at hand. Not who reported what when. I found that bug when it hit me and noticed that it had been reported. I thanked the Gods that yo= u were working on it, that I hadn't attempted to upgrade a production box, and went about my business avoiding it by installing from stage1. --=20 gentoo-dev@gentoo.org mailing list