From owner-freebsd-current Sun Sep 1 14:58:14 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 8F80E37B400; Sun, 1 Sep 2002 14:58:07 -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 F1B6E43E6E; Sun, 1 Sep 2002 14:58:06 -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 g81LvxOB070868; Sun, 1 Sep 2002 17:57:59 -0400 (EDT) (envelope-from ak03@kanpc.gte.com) Received: (from ak03@localhost) by kanpc.gte.com (8.12.6/8.12.5/Submit) id g81LvxhM070867; Sun, 1 Sep 2002 17:57:59 -0400 (EDT) Date: Sun, 1 Sep 2002 17:57:59 -0400 From: Alexander Kabaev To: Cc: current@FreeBSD.org, developers@FreeBSD.org Subject: Re: HEADS UP: GCC 3.2 in progress Message-Id: <20020901175759.24d5b9a2.ak03@gte.com> In-Reply-To: <20020901144645.A16984-100000@wonky.feral.com> References: <20020901173956.7b23a223.ak03@gte.com> <20020901144645.A16984-100000@wonky.feral.com> Organization: Verizon Data Services X-Mailer: Sylpheed version 0.8.2claws11 (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 On Sun, 1 Sep 2002 14:50:50 -0700 (PDT) Matthew Jacob wrote: > From recent experience it is my estimation that a gcc upgrade sets 5.0 > development back a month (that is, the last GCC upgrade kept *me* from > working productively for around a month due to various this thats and > the others). If that's what people want, that's fine. I could also be > totally wrong, and this won't break things. I'm just a bit startled > that this appears out of nowhere (I sure don't recall it being > discussed) and just happens, with 10 minutes warning. Matt, the change was discussed several times on developers@, so this import is hardly 'out of nowhere'. > This is, IMO, why FreeBSD is not going to be very successful. You > cannot just make major toolchain changes w/o at least *some* belief > that this is going to be done well. Did you do a dryrun with the > import before checking things in? About five buildworlds on i386 and two on Alpha. Does that count as dry runs? -- Alexander Kabaev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message