Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Tue, 30 Jan 2001 15:44:33 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: -mno-cygwin and c++ stl... progress? Message-ID: <20010130154433.A24216@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20010130154042 DOT B24083 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <20010130154042.B24083@redhat.com>; from cgf@redhat.com on Tue, Jan 30, 2001 at 03:40:42PM -0500 On Tue, Jan 30, 2001 at 03:40:42PM -0500, Christopher Faylor wrote: >On Tue, Jan 30, 2001 at 02:37:51PM -0600, Mumit Khan wrote: >>(1) libgcc.a built for Cygwin may or may reference __impure_ptr from >>Cygwin DLL even if you don't *think* you're using exceptions (long >>story, the keyword here is inhibit_libc), > >Hopefully, I have worked around this in recent gcc 2.95.* releases so it >shouldn't be a problem. > >>and (2) the C++ runtime library for Cygwin and Mingw are *not* >>compatible. > >This one is the show stopper. Or, rather, it is the current stumbling block. I'm willing to release a libstdc++.a for mingw. It will be trivial to do this now that we've split out the include and lib directories for mingw. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple