X-Spam-Check-By:	sourceware.org
From:	kenelson8 AT comcast DOT net
To:	cygwin AT cygwin DOT com
Subject:	Re: g++ 3.4.4, mingw32, exceptions and threads
Date:	Thu, 22 Jun 2006 20:25:12 +0000
Message-Id:	<062220062025.1754.449AFCA7000D7BFA000006DA2200761064C802019C040A020A05@comcast.net>
X-Mailer:	AT&T Message Center Version 1 (Apr 11 2006)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

The mingw32 was distributed with cygwin (al la gcc-mingw-g++).   g++
obviously has an option for threadsafe exceptions, as I have used them
in the past.  So if this isn't the place to inquire about the build options 
used to make the gcc-mingw-* packages distributed with cygwin
then where is?

And the reason for using windows-isms is obvious in that it wouldn't
work with -mno-cygwin if it wasn't using windows-ism.   THe libraries 
I am linking to are filled with them and thus rather than try to mix
and match, it is best to disable the link to the cygwin library.

--Karl

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -