From owner-freebsd-current Sun Apr 4 6:22:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 13ADE14D8C for ; Sun, 4 Apr 1999 06:22:49 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id PAA09482 for current@FreeBSD.ORG; Sun, 4 Apr 1999 15:20:50 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id F01518848; Sun, 4 Apr 1999 13:43:30 +0200 (CEST) Date: Sun, 4 Apr 1999 13:43:30 +0200 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: X problems using egcs as compiler Message-ID: <19990404134330.B3397@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG References: <19990403225146.A99040@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: ; from Alex Zepeda on Sat, Apr 03, 1999 at 01:47:11PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5173 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Alex Zepeda: > Personally, I'd vote for using the new runtime objects, and forcing binary > incompatibility. It's worth it IMO for the exception handling support if > nothing else. However, if you're dead set against it, just back up your > runtime objects, and edit the spec file (like the egcs port forced you to > do at one time, and probably still does). The problem I see is that exceptions are for C++ and forcing ANSI C files to be compiled with -fexceptions and linked with new runtime objects is probably not the best way... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #70: Sat Feb 27 09:43:08 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message