Date: Thu, 6 Jun 2002 10:14:52 -0700 From: "David O'Brien" <obrien@freebsd.org> To: Sheldon Hearn <sheldonh@starjuice.net> Cc: Christopher Nehren <apeiron@prophecy.dyndns.org>, current@freebsd.org Subject: Re: "Safe" to go to -CURRENT? Message-ID: <20020606101452.F59829@dragon.nuxi.com> In-Reply-To: <1626.1023353655@axl.seasidesoftware.co.za>; from sheldonh@starjuice.net on Thu, Jun 06, 2002 at 10:54:15AM %2B0200 References: <1023266819.500.6.camel@prophecy.dyndns.org> <1626.1023353655@axl.seasidesoftware.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jun 06, 2002 at 10:54:15AM +0200, Sheldon Hearn wrote: > > I've been monitoring the -CURRENT mailing list for about a day or two, > > and haven't seen anything that's really broken (except for GCC 3.x, > > which I don't use anyway). So, is it "safe" to upgrade to -CURRENT yet? > > TIA for the info, > > Chris > > There are still issues with the C++ compiler in the base system that > make building X and some other C++ ports tricky. There is no issue with the C++ compiler. There is issue with the X source that uses depreciated features. 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?20020606101452.F59829>