Date: Sun, 28 Feb 1999 15:29:09 -0800 From: "David O'Brien" <obrien@NUXI.com> To: Chuck Robey <chuckr@mat.net> Cc: freebsd-current@FreeBSD.ORG Subject: Re: gcc Message-ID: <19990228152909.E2170@relay.nuxi.com> In-Reply-To: <Pine.BSF.4.10.9902281751060.339-100000@picnic.mat.net>; from Chuck Robey on Sun, Feb 28, 1999 at 06:04:41PM -0500 References: <31170.920242197@zippy.cdrom.com> <Pine.BSF.4.10.9902281751060.339-100000@picnic.mat.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> I keep on hearing about how we're losing because we don't have the 3 > month old latest feature With EGCS the issue isn't having the latest 3 mo. feature, but we have a totally BROKEN C++ compiler. The STL with it is broken, and it is so far from the ISO C++ standard, it really can't be called C++ any longer. > Every time I see a post that is one-sidedly aimed towards the latest > untested thing I'm working on the egcs 1.1.x branch. I wouldn't go near their HEAD branch for FreeBSD use. I distrust that code more than I do Micro$oft's. > Yes, let's try egcs. I want to do buildworlds/installworlds/new kernel > builds here with it for a while. What I have won't build kernels yet. I could hack our system Makefiles to use different compile options, but I don't like that approach. So I'm working on adding our compiler flags and such. > Could I install egcs out of ports, and do that testing? I want to do > that, if it would contribute. Last I tried, no. IMHO, we are a ways off, but we need to at least be working on it. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) 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?19990228152909.E2170>