From owner-freebsd-ports Sun Nov 28 21: 5:52 1999 Delivered-To: freebsd-ports@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 14E891548B for ; Sun, 28 Nov 1999 21:05:46 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id VAA15021; Sun, 28 Nov 1999 21:05:38 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id VAA54541; Sun, 28 Nov 1999 21:05:37 -0800 (PST) (envelope-from obrien) Date: Sun, 28 Nov 1999 21:05:37 -0800 From: "David O'Brien" To: Will Andrews Cc: Ade Lovett , freebsd-ports@FreeBSD.org, Bill Fumerola , "Chris D. Faulhaber" Subject: Re: ports/15135: new port: devel/cervisia Message-ID: <19991128210537.A54056@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <19991128201850.A61560@lovett.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from andrews@TECHNOLOGIST.COM on Sun, Nov 28, 1999 at 09:35:16PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Nov 28, 1999 at 09:35:16PM -0500, Will Andrews wrote: > frankly, I've wondered why gcc 2.91.66 wasn't MFC'd to 3.x long ago > (David?). After all, it's been in -CURRENT for several months (at the > very least). I guess I'm not so agaist it as I was. I was asked if I thought a MFC for 3.3 was reasonable. I said no. My real concern is that parts of the kernel and userland had to be tweaked when I brought in EGCS. I don't know what those changes were at this point. So it is more effort than just a MFC for the compiler. > the earliest version (that I know of) which supports the newer ANSI ISO C++ > standards. That is, the new standard apparently not supported by the > older gcc. I'm confused why the `egcs' port can't be used in -STABLE. That ports gives you GCC 2.95.2, with many of the FreeBSD specific changes. > Can we not MFC gcc 2.91.66 to RELENG_3 for a future version of 3.x? We are approaching code freeze for 3.4, so there certainly isn't time to MFC for 3.4. My guess is that 3.5 will be the last 3.x released version. So it isn't worth the effort at that point. > > If such a change does happen, it may also be worth considering synchronising > > it with a move to USE_NEWGCC for the GNOME metaport I personally see this as the best approach, and one that doesn't really cause any problems. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message