From owner-freebsd-current Thu Aug 15 11: 9:17 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 752D137B400 for ; Thu, 15 Aug 2002 11:09:15 -0700 (PDT) Received: from h132-197-179-27.gte.com (h132-197-179-27.gte.com [132.197.179.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE70943E42 for ; Thu, 15 Aug 2002 11:09:14 -0700 (PDT) (envelope-from ak03@gte.com) Received: from kanpc.gte.com (localhost [IPv6:::1]) by h132-197-179-27.gte.com (8.12.5/8.12.5) with ESMTP id g7FI9CDg084012; Thu, 15 Aug 2002 14:09:12 -0400 (EDT) (envelope-from ak03@kanpc.gte.com) Received: (from ak03@localhost) by kanpc.gte.com (8.12.5/8.12.5/Submit) id g7FI9CkB084011; Thu, 15 Aug 2002 14:09:12 -0400 (EDT) Date: Thu, 15 Aug 2002 14:09:11 -0400 From: Alexander Kabaev To: "Long, Scott" Cc: jesse_gross@yahoo.com, current@FreeBSD.ORG Subject: Re: GCC 3.2 Message-Id: <20020815140911.7da2c3da.ak03@gte.com> In-Reply-To: <2C7CBDC6EA58D6119E4A00065B3A24CB046492@btcexc01.btc.adaptec.com> References: <2C7CBDC6EA58D6119E4A00065B3A24CB046492@btcexc01.btc.adaptec.com> Organization: Verizon Data Services X-Mailer: Sylpheed version 0.8.1claws52 (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Yes, moving to gcc32 is highly desirable for -current, otherwise we > will be stuck at gcc311 for the entire life of FreeBSD 5.x. The > important question to ask is, who will do the dirty work? Moving to GCC 3.2 will do us no good. The lifetime of the 3.2 release will be pretty short and 3.3 is supposed to replace it pretty soon. If we stick with 3.2 in -CURRENT, we'll find ourself tied to an old and unsupported release for the whole 5.x line, i.e. we'll risk to repeat 2.95.x story yet again. David O'Brien proposes to move -CURRENT directly to the 3.3 CVS shanshots, bypassing the GCC 3.2 version altogether. Early FreeBSD 5.x release(s) will not be polished for general consumption anyway, so that makes sense. By the time FreeBSD stabilizes, GCC 3.3 release will be ready. -- Alexander Kabaev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message