Date: Sun, 1 Sep 2002 17:57:59 -0400 From: Alexander Kabaev <ak03@gte.com> To: <mjacob@feral.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 1 Sep 2002 14:50:50 -0700 (PDT) Matthew Jacob <mjacob@feral.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020901175759.24d5b9a2.ak03>