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 X-Authentication-Warning: hp2.xraylith.wisc.edu: khan owned process doing -bs Date: Tue, 30 Jan 2001 14:37:51 -0600 (CST) From: Mumit Khan To: Christopher Abbey cc: cygwin AT sources DOT redhat DOT com Subject: Re: -mno-cygwin and c++ stl... progress? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 30 Jan 2001, Christopher Abbey wrote: > Seeing the assert.h patch flow by reminded me that a while ago > (November maybe?) Earnie mentioned something about work being > under way to enable the subject combination by way of some > additional packages for the libraries needed to compile for > msvc targets. I was just wondering how that work had progressed? I'm not I understand what you're referring to. Contrary to some opinion out there, -mno-cygwin *in general* does not work for C++ code unless you have the appropriate target libraries from Mingw distribution. The reason is twofold -- (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), and (2) the C++ runtime library for Cygwin and Mingw are *not* compatible. > I've been using the mingw builds Mumit has on xraylith, but > have noticed some, uh, "issues" with them and was wondering > if the time was right to look at a different cross compiling > environment. (Mo setup the one I'm using now, so it's functional > within limits....) Please elaborate on the issues so that I can remedy these. Regards, Mumit -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple