From owner-freebsd-current Sat Apr 3 16: 5:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 0146B14E7B for ; Sat, 3 Apr 1999 16:05:08 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id SAA02202; Sat, 3 Apr 1999 18:03:12 -0600 (CST) Date: Sat, 3 Apr 1999 18:03:12 -0600 (CST) From: Steve Price To: "David O'Brien" Cc: current@FreeBSD.ORG Subject: Re: X problems using egcs as compiler In-Reply-To: <19990403141824.B73304@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 3 Apr 1999, David O'Brien wrote: # I'm not sure the best way to approach this. The specification file used # in the port is different from the one that will be in the base system. # (the on in the Port is more stock EGCS) The base system will have many # more of our hacks. I don't know what we'd prove if the ports tree was built with an un-FreeBSD'd egcs. It might get us close, then again it might get us chasing (mis)features that aren't going to be present when it is the system compiler. I certainly would feel better about using the real thing. # So the fix we mentioned might not be needed with the base EGCS. Maybe # you can just compile all the ports just to see where we stand. I don't # expect *any* problems with ports that use the C compiler. All the # problems I think we might have are C++ compiler issues. See above. Can you send me a set of instructions for turning gcc off and egcs on in the base distribution? -steve # -- # -- 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