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 1F1xPv-0004XI-27 for garchives@archives.gentoo.org; Thu, 26 Jan 2006 03:03:23 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id k0Q329lL027681; Thu, 26 Jan 2006 03:02:09 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 k0Q2xiEF022814 for ; Thu, 26 Jan 2006 02:59:44 GMT Received: from localhost ([127.0.0.1] helo=home.wh0rd.org) by smtp.gentoo.org with esmtp (Exim 4.54) id 1F1xMN-0006Yi-TR for gentoo-dev@lists.gentoo.org; Thu, 26 Jan 2006 02:59:44 +0000 Received: (qmail 28085 invoked from network); 25 Jan 2006 21:52:28 -0500 Received: from unknown (HELO vapier) (192.168.0.2) by 192.168.0.1 with SMTP; 25 Jan 2006 21:52:28 -0500 From: Mike Frysinger Organization: wh0rd.org To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: bootstrapping since gcc 3.4 is stable Date: Wed, 25 Jan 2006 22:02:12 -0500 User-Agent: KMail/1.9 References: <200601252251.k0PMpKZZ004307@gw.open-hosting.net> In-Reply-To: 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" Content-Disposition: inline Message-Id: <200601252202.13012.vapier@gentoo.org> X-MIME-Autoconverted: from quoted-printable to 8bit by robin.gentoo.org id k0Q2xiEF022814 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by robin.gentoo.org id k0Q329mq027681 X-Archives-Salt: bac0049a-8f7d-4f67-adb0-77673d0b4026 X-Archives-Hash: e7b2cd41bbd8a13e6a9b7d0d5102a23c On Wednesday 25 January 2006 21:40, Sven K=F6hler wrote: > I expected the result of these steps to be a "clean" system. > > What do i mean with a "clean" system? > > Actually i thought, that i mean the result of a "emerge -e system" - bu= t > i know now, that this is not what i mean. For example "emerge -e system= " > sometimes choses to install gcc-3.3 instead of the "default" libstdc++-= v3. what you want to happen just isnt feasible at this point in time (if it e= ver=20 will be) portage does not automatically change the version of gcc across major=20 versions ... this is done on purpose as there is no way of knowing whethe= r=20 the user wants the new version of gcc to be the default system one or whe= ther=20 they are just installing a new one for fun you want bootstrap.sh to basically automatically run `emerge gcc && emerg= e=20 prune gcc` ... this is not doable as packages may be tied to the older=20 version of gcc ... and in fact, python itself currently links against=20 libstdc++, so if bootstrap followed the automated steps listed above, you= 'd=20 end up with a broken python (and thus a broken emerge) thus, in order to get a "clean" system you're so keen on, you need to run= =20 bootstrap.sh to get a 3.4 compiler, switch your default compiler to 3.4,=20 rebuild anything that is linked against 3.3 with 3.4, prune 3.3 from your= =20 system, and then continue on with the `emerge -e system` -mike --=20 gentoo-dev@gentoo.org mailing list