From owner-freebsd-ports Sun Nov 28 21:31:36 1999 Delivered-To: freebsd-ports@freebsd.org Received: from pluto.psn.net (pluto.psn.net [207.211.58.12]) by hub.freebsd.org (Postfix) with ESMTP id 9A8E015435 for ; Sun, 28 Nov 1999 21:31:34 -0800 (PST) (envelope-from will@shadow.blackdawn.com) Received: from 5042-243.008.popsite.net ([209.224.140.243] helo=shadow.blackdawn.com) by pluto.psn.net with esmtp (PSN Internet Service 3.03 #1) id 11sJPL-0002sz-00; Sun, 28 Nov 1999 22:31:29 -0700 Received: (from will@localhost) by shadow.blackdawn.com (8.9.3/8.9.3) id AAA37718; Mon, 29 Nov 1999 00:31:05 -0500 (EST) (envelope-from will) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19991128210537.A54056@dragon.nuxi.com> Date: Mon, 29 Nov 1999 00:31:05 -0500 (EST) Reply-To: Will Andrews From: Will Andrews To: "David O'Brien" Subject: Re: ports/15135: new port: devel/cervisia Cc: "Chris D. Faulhaber" , Bill Fumerola , freebsd-ports@FreeBSD.org, Ade Lovett Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 29-Nov-99 David O'Brien wrote: > 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. I agree totally with you on this point. >> 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. I didn't say it can't be used. See below. >> > 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. Right. The problem here is that the KDE and Qt port maintainers seem reluctant to put the switch in the kdelibs11 and qt142 ports so that those ports will be compiled using the newer g++.. required for certain aforementioned apps. I think the sooner, the better. Oh well if people have to recompile their libraries with NEWGCC, right? :-) The reason I asked about MFC'ing egcs 1.1.2 is because it would eliminate the need to have USE_NEWGCC in the ports system. Of course, that is the _only_ reason I asked. And quite frankly, I don't like the idea myself. People, let's move on, upgrade those ports! What more convincing evidence do we need? -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message