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 1EhSpf-0004AG-D5
for garchives@archives.gentoo.org; Wed, 30 Nov 2005 14:21:15 +0000
Received: from robin.gentoo.org (localhost [127.0.0.1])
by robin.gentoo.org (8.13.5/8.13.5) with SMTP id jAUEJoLF006357;
Wed, 30 Nov 2005 14:19:50 GMT
Received: from dime82.dizinc.com (dime82.dizinc.com [72.29.73.203] (may be forged))
by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id jAUEGc2O011367
for <gentoo-dev@lists.gentoo.org>; Wed, 30 Nov 2005 14:16:38 GMT
Received: from tuxp3 by dime82.dizinc.com with local (Exim 4.52)
id 1EhSlE-00031T-Ew
for gentoo-dev@lists.gentoo.org; Wed, 30 Nov 2005 09:16:40 -0500
Received: from 141.149.132.61 ([141.149.132.61])
(SquirrelMail authenticated user tuxp3@leetworks.com)
by www.leetworks.com with HTTP;
Wed, 30 Nov 2005 09:16:40 -0500 (EST)
Message-ID: <1873.141.149.132.61.1133360200.squirrel@www.leetworks.com>
In-Reply-To: <1133359566.5990.3.camel@cgianelloni.nuvox.net>
References: <20051128142233.GA19195@aerie.halcy0n.com>
<200511291501.42275.mike@gaima.co.uk>
<1133278747.13876.26.camel@cgianelloni.nuvox.net>
<438D2D88.7030004@leetworks.com>
<1133359566.5990.3.camel@cgianelloni.nuvox.net>
Date: Wed, 30 Nov 2005 09:16:40 -0500 (EST)
Subject: Re: [gentoo-dev] Moving GCC-3.4 to stable on x86
From: tuxp3@leetworks.com
To: gentoo-dev@lists.gentoo.org
User-Agent: SquirrelMail/1.4.4
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
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-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - dime82.dizinc.com
X-AntiAbuse: Original Domain - lists.gentoo.org
X-AntiAbuse: Originator/Caller UID/GID - [32707 32003] / [47 12]
X-AntiAbuse: Sender Address Domain - leetworks.com
X-Source: /usr/local/cpanel/3rdparty/bin/php
X-Source-Args: /usr/local/cpanel/3rdparty/bin/php /usr/local/cpanel/base/3rdparty/squirrelmail/src/compose.php
X-Source-Dir: :/base/3rdparty/squirrelmail/src
X-Archives-Salt: 231b59d8-404c-4da5-868a-b2f51de1bf45
X-Archives-Hash: 50bb170956af932c28347621f832606f
> On Tue, 2005-11-29 at 23:41 -0500, Andrew Muraco wrote:
>> Out of curiosity, if this goes into effect before 2006.0 is released,
>> then ALL the stages for x86 and the livecd would be built with gcc34? If
>> so then I think this may benefit alot of users, especially ones that do
>> a stage1/2 just so they can shove gcc34 into there system at an early
>> stage. Also, if gcc34 gets moved to x86, would gcc40 be ~x86? This I see
>> as a bigger problem for those of us that are already running gcc34. But
>> I'm sure many ~x86 users would welcome that, after all what fun is ~x86
>> without some breakage every now and then ;-)
>
> 2006.0 is still a ways off, but yes, all of the stages would be built
> with gcc 3.4 exclusively. Of course, this would happen whether we made
> the change globally (for x86) or if we only did it via profile. The
> problem with doing it via profile is we *already have* people on 2005.0
> and 2005.1 profiles running gcc 3.4, so it means causing a much more
> disruptive upgrade for all ~x86 users, or anyone who has merged gcc 3.4
> explicitly already.
>
> --
> Chris Gianelloni
> Release Engineering - Strategic Lead
> x86 Architecture Team
> Games - Developer
> Gentoo Linux
Again, would anyone know what will happen to ~x86 gcc?, Will it become
gcc40 or just use the stable x86 gcc for everyone? (except those who are
already playing with gcc40 at their own risk)
Tux
--
gentoo-dev@gentoo.org mailing list