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: Wed, 13 Jun 2001 00:26:56 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: MinGW vs. -mno-cygwin (Was: GCC 2.95.3-4 Problem) Message-ID: <20010613002656.D4531@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <5.1.0.14.0.20010613104400.00a12150@192.168.1.1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <5.1.0.14.0.20010613104400.00a12150@192.168.1.1>; from ecognito1@earthcorp.com on Wed, Jun 13, 2001 at 10:46:36AM +1000 On Wed, Jun 13, 2001 at 10:46:36AM +1000, E wrote: >cfg wrote: >>So, probably the FAQ should suggest that -mno-cygwin uses a >>subset of the functionality found at www.mingw.org. Before people >>report problems with -mno-cygwin they should 1) check the cygwin >>mailing list archives and 2) check the mingw web site. Also, adding >>words about the libstdc++.a library might help. > >Also including a link to > >which describes how to get around the libstdc++.a problems may also be useful. No. This is riddled with out-of-date information. We shouldn't be linking to *anything* which mentions B20.1. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple