Date: Wed, 18 Oct 2000 15:15:52 -0700 From: "David O'Brien" <obrien@freebsd.org> To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> Cc: Szilveszter Adam <sziszi@petra.hos.u-szeged.hu>, Konstantin Chuguev <Konstantin.Chuguev@dante.org.uk>, freebsd-emulation@freebsd.org, freebsd-current@freebsd.org Subject: Re: Which GCC in CURRENT? [Was: Re: Wine update] Message-ID: <20001018151552.C71459@dragon.nuxi.com> In-Reply-To: <Pine.BSF.4.21.0010161257500.19548-100000@taygeta.dbai.tuwien.ac.at>; from pfeifer@dbai.tuwien.ac.at on Mon, Oct 16, 2000 at 01:21:33PM %2B0200 References: <20001016115842.F4302@petra.hos.u-szeged.hu> <Pine.BSF.4.21.0010161257500.19548-100000@taygeta.dbai.tuwien.ac.at>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Oct 16, 2000 at 01:21:33PM +0200, Gerald Pfeifer wrote: > On Mon, 16 Oct 2000, Szilveszter Adam wrote: > > Also, since 2.96 has not even been released yet, I assume the > > maintainer (bruce, AFAIK) just makes sure that it builds and compiles > > stuff OK and so by the time 5.0 will be released and hopefully 2.96 > > too, we just have to push the button and it will be there. > > I can assert, with utmost authority ;-), that GCC 2.96 will never be > released by the GCC team. Correct, and FreeBSD 5.0 will ship with 5.0+ release. The import and use of GCC 2.96(7) in FreeBSD-CURRENT is to support development of the IA-64, x86-64, and PPC ports. Since FreeBSD-CURRENT is not a release and is a tool to use in getting to 5.0, we didn't mind importing a non-released version of GCC. Note that FreeBSD's warning of don't expect stability in -CURRENT will also be very true of the this compiler. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001018151552.C71459>