From owner-freebsd-current Sat Apr 3 14:47:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 1436F14D42 for ; Sat, 3 Apr 1999 14:47:34 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id OAA57143; Sat, 3 Apr 1999 14:44:13 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199904032244.OAA57143@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: obrien@NUXI.com Cc: Ollivier Robert , current@FreeBSD.ORG Subject: Re: X problems using egcs as compiler In-reply-to: Your message of "Sat, 03 Apr 1999 14:34:33 PST." <19990403143433.A73396@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 03 Apr 1999 14:44:13 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, it is most likely a DWARF2_UNWIND issue at least that is what I concluded in trying to support Electric Fire also someone should investigate whether egcs supports exception handling without thread support if memory does not fail me egcs requires thread support for exception handling. Perhaps it is a good time to review the egcs docs with respect to frame handling and exception handling. Amancio > > The problem is that egcs 1.1.2 has its own crt*.o files and use them in > > place of the FreeBSD one. By moving the files elsewhere, it works. I don't > > know the effect on exceptions though. > > If that is the problem, then it sounds like a DWARF2_UNWIND issue. > > > I don't know what David plan to do with these crt*.o files. David ? > > src/lib/csu/i386-elf will build and install crtbegin.o and crtend.o from > the EGCS sources. Otherwise we have to use the poorer exception > unwinding method. > > -- > -- 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