Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
X-Authentication-Warning:	hp2.xraylith.wisc.edu: khan owned process doing -bs
Date:	Tue, 30 Jan 2001 15:19:07 -0600 (CST)
From:	Mumit Khan <khan AT NanoTech DOT Wisc DOT EDU>
To:	cygwin AT cygwin DOT com
Subject:	Re: -mno-cygwin and c++ stl... progress?
In-Reply-To:	<20010130154042.B24083@redhat.com>
Message-ID:	<Pine.HPP.3.96.1010130151455.2988I-100000@hp2.xraylith.wisc.edu>
MIME-Version:	1.0

On Tue, 30 Jan 2001, Christopher Faylor wrote:

> On Tue, Jan 30, 2001 at 02:37:51PM -0600, Mumit Khan wrote:
> Hopefully, I have worked around this in recent gcc 2.95.* releases so it
> shouldn't be a problem.

The workaround you mention only applies to building the mingw specific
bits in Cygwin/Winsup, and not applicable to general class of C++ code.

FYI, libstdc++-v3, as part of gcc-2.97, uses exceptions internally, and 
the current code will pull in various bits of eh.o(libgcc.a), even when 
building winsup/cinstall with exceptions rtti etc turned off. I may have 
a workaround/solution, but haven't tested it yet.

> >and (2) the C++ runtime library for Cygwin and Mingw are *not*
> >compatible.
> 
> This one is the show stopper.

And there is nothing we should do about it other than inform users that it
is to be expected and exactly what the remedy is. 

Regards,
Mumit



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -