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
Date: Tue, 30 Jan 2001 18:03:54 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: -mno-cygwin and c++ stl... progress?
Message-ID: <20010130180354.A21050@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20010130163440 DOT A24655 AT redhat DOT com> <Pine DOT HPP DOT 3 DOT 96 DOT 1010130162051 DOT 2988N-100000 AT hp2 DOT xraylith DOT wisc DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <Pine.HPP.3.96.1010130162051.2988N-100000@hp2.xraylith.wisc.edu>; from khan@NanoTech.Wisc.EDU on Tue, Jan 30, 2001 at 04:21:39PM -0600

On Tue, Jan 30, 2001 at 04:21:39PM -0600, Mumit Khan wrote:
>On Tue, 30 Jan 2001, Christopher Faylor wrote:
>>I was actually thinking of the pragmatic solution of checking in a
>>libstdc++.a file into the mingw repository and releasing that along
>>with the mingw stuff.  I assume that libstdc++.a would be produced by a
>>true mingw gcc.
>
>Now, that's much better.  I would of course then like to see mingw
>libgcc.a included as well, unless we can reasonably guarantee that it
>won't be needed.

I've removed the last two impure_ptr's from libgcc.a in gcc 2.95.2-7.

cgf

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