Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT cygwin DOT com Date: Tue, 22 Jan 2002 11:23:07 -0500 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: gcc v3 issue -- hacky solution Message-ID: <20020122162307.GB14458@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <20020122032839 DOT GA23746 AT redhat DOT com> <08d401c1a2f4$d2d66370$0200a8c0 AT lifelesswks> <20020122034231 DOT GA23893 AT redhat DOT com> <08e601c1a2f7$35b39d30$0200a8c0 AT lifelesswks> <20020122035327 DOT GA24224 AT redhat DOT com> <3C4D5D6E DOT 4D0D99A AT yahoo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C4D5D6E.4D0D99A@yahoo.com> User-Agent: Mutt/1.3.23.1i On Tue, Jan 22, 2002 at 07:39:10AM -0500, Earnie Boyd wrote: >Christopher Faylor wrote: >> >> On Tue, Jan 22, 2002 at 02:45:17PM +1100, Robert Collins wrote: >> >Or maybe Danny Smith can provide details on what it takes to build said >> >library, and one of the folk that keep building gcc for-the-hell-of-it >> >and talking on cygwin@ can become the maintainer? >> >> It's easy enough to build the library for mingw. There's no trick there. >> > >Right, but the trick is using exceptions. You'll need a libgcc.dll to >accomplish exceptions across dll boundaries. However, if the exceptions >remain local then the static libgcc.a should work. Agh. Good point. I forgot that you needed a DLL to properly deal with exceptions. That complicates things even more. cgf