From owner-freebsd-hackers Sat Jan 16 14:15:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28793 for freebsd-hackers-outgoing; Sat, 16 Jan 1999 14:15:35 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.dyn.ml.org (sf3-50.ppp.wenet.net [206.15.84.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28787 for ; Sat, 16 Jan 1999 14:15:33 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@zippy.dyn.ml.org [127.0.0.1]) by zippy.dyn.ml.org (8.9.1/8.8.8) with ESMTP id OAA07361; Sat, 16 Jan 1999 14:18:40 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Sat, 16 Jan 1999 14:18:40 -0800 (PST) From: Alex Zepeda X-Sender: garbanzo@zippy.dyn.ml.org To: Stefan Veith cc: hackers@FreeBSD.ORG Subject: Re: Problems with egcs-1.1.1 port In-Reply-To: <36A09E81.8DF04971@bigfoot.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 16 Jan 1999, Stefan Veith wrote: > I installed the egcs-1.1.1 port on my system (3.0-R) and tried to > compile a programme which uses extentions. But I did not succed to > compile it properly so far. The configure script of mico for example > tries to test the extention capability of egcs and causes a core dump. By extensions do you perhaps mean exceptions? > Is this a known problem? Is there any possibility to compile programmes > with extensions under FreeBSD? Ok here's the deal. Exceptions in egcs (and probably gcc 2.8) have their own requirements. Since they manipulate the stack, and attempt to be thread safe, and all sorts of other fun stuff, etc, they've come up with their own incompatable way of doing things. This is fine, but requires some tweaking of egcs 1.1.1 when you build it. Not fun. There is somewhat of a solution, and that is to use setjmp and longjmp to handle exceptions. You can do this by adding the switch -fsjlj-exceptions to the CXXFLAGS before you run configure. Also keep in mind that without any effort, shared libs are somewhat broken, so to make sure mico builds, you'll want to use --disable-shared on the configure command line. What in the world are you trying to build that needs mico? If it's koffice, make sure you configure mico with --disable-ministl (or whatever it's called to make sure that the half hearted implementation of the STL isn't used). - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message