Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Tue, 30 Jan 2001 16:21:08 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: -mno-cygwin and c++ stl... progress? Message-ID: <20010130162108.B24511@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20010130154042.B24083@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: ; from khan@NanoTech.Wisc.EDU on Tue, Jan 30, 2001 at 03:19:07PM -0600 On Tue, Jan 30, 2001 at 03:19:07PM -0600, Mumit Khan wrote: >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. I actually thought that I'd removed all occurrences of impure_ptr from libgcc.a but I see that two still remain. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple