Message-Id:	<200005312226.SAA29600@delorie.com>
Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
From:	"Parker, Ron" <rdparker AT butlermfg DOT com>
To:	Ross Smith <ross DOT s AT ihug DOT co DOT nz>, cygwin AT sourceware DOT cygnus DOT com
Subject:	RE: Major bug -- Exception handling broken
Date:	Wed, 31 May 2000 17:23:27 -0500
MIME-Version:	1.0
X-Mailer:	Internet Mail Service (5.5.2448.0)

------_=_NextPart_000_01BFCB4F.2AD8B696
Content-Type: text/plain;
	charset="iso-8859-1"

> Thanks, that seems to work. Are there any gotchas I need to watch out
> for when doing it this way? That is, are there any differences between
> invoking via gcc vs g++ that aren't accounted for by adding -lstdc++
> to the link step?

Not that I am aware of.  The verbose output from gcc and g++ looks identical
other than the -lstdc++ option.


------_=_NextPart_000_01BFCB4F.2AD8B696
Content-Type: text/plain; charset=us-ascii

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
------_=_NextPart_000_01BFCB4F.2AD8B696--

- Raw text -