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
X-Authentication-Warning: hp2.xraylith.wisc.edu: khan owned process doing -bs
Date: Tue, 30 Jan 2001 15:27:35 -0600 (CST)
From: Mumit Khan <khan AT NanoTech DOT Wisc DOT EDU>
To: cygwin AT cygwin DOT com
Subject: Re: -mno-cygwin and c++ stl... progress?
In-Reply-To: <20010130154433.A24216@redhat.com>
Message-ID: <Pine.HPP.3.96.1010130152121.2988J-100000@hp2.xraylith.wisc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

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!

Regards,
Mumit



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