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 16:34:40 -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: <20010130163440.A24655@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20010130154433 DOT A24216 AT redhat DOT com> <Pine DOT HPP DOT 3 DOT 96 DOT 1010130152121 DOT 2988J-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.1010130152121.2988J-100000@hp2.xraylith.wisc.edu>; from khan@NanoTech.Wisc.EDU on Tue, Jan 30, 2001 at 03:27:35PM -0600

On Tue, Jan 30, 2001 at 03:27:35PM -0600, Mumit Khan wrote:
>On Tue, 30 Jan 2001, Christopher Faylor wrote:
>>>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.
>
>Hmmm ... this issue came up way back, and I remember suggesting that we
>consider using multilib facility in GCC build process to accomplish this.
>It's not too hard to get working, other than of course the fact that it 
>takes twice as long to build.  However, multilib-ing has one big con --
>not that many people understand how it works in gcc. Any other solution
>of trying to build two copies of libstdc++, with slightly different
>options, may not be clean. Also, you'll again run into the same problem
>with libstdc++-v3 needing exception handling code, and libgcc supplying
>it for the wrong runtime!

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.

cgf

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