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 1F1tHw-00012C-Uh for garchives@archives.gentoo.org; Wed, 25 Jan 2006 22:38:53 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id k0PMbw6r024178; Wed, 25 Jan 2006 22:37:58 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 k0PMZwlY022959 for ; Wed, 25 Jan 2006 22:36:01 GMT Received: from speedy.apps4med.net ([66.139.177.227]) by gw.open-hosting.net (8.13.4/8.13.3) with ESMTP id k0PMZi2C004122 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 25 Jan 2006 16:35:54 -0600 Message-Id: <200601252235.k0PMZi2C004122@gw.open-hosting.net> From: MIkey Subject: [gentoo-dev] Re: Re: bootstrapping since gcc 3.4 is stable To: gentoo-dev@lists.gentoo.org Date: Wed, 25 Jan 2006 16:31:38 -0600 References: <1138197403.10589.1.camel@cgianelloni.nuvox.net> <1138225963.10589.16.camel@cgianelloni.nuvox.net> 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=us-ascii Content-Transfer-Encoding: 7Bit 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 X-Archives-Salt: f381e0b5-a6d8-4093-bdbd-ce241d8037b7 X-Archives-Hash: fde3cd4af27e9c31f6a15dc4f01cfbf2 Chris Gianelloni wrote: > Which you won't have to deal with for long, 2006.0 is being worked on as > we speak. The basic jist of this is that what you are seeing is pretty > much expected behavior for bootstrapping using a stage with an older > GCC. The way I read it, the gcc-3.4.4-r1.ebuild includes a dependency on libstdc++-v3 and =sys-devel/gcc-3.3* if "build" is not in your USE environment. The bootstrap during bootstrap.sh sets that build flag. Any subsequent installs of gcc-3.4.4-r1 are going to install libstdc++-v3, no matter what you do (at least x86 users). Or maybe I am just reading that PDEPEND wrong. Regardless, I have never had to mask out lower versions of gcc before. I assumed the reason for the dependency was a half ass attempt to keep idiots from thoughtlessly destroying their toolchain. -- gentoo-dev@gentoo.org mailing list