Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: Thu, 29 Mar 2001 22:03:14 -0600 (CST) From: Mumit Khan To: cygwin AT cygwin DOT com Subject: Re: -mno-cygwin and C++ -- solved! In-Reply-To: <20010328223246.A4677@redhat.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 28 Mar 2001, Christopher Faylor wrote: > Sometimes I think that the best way to handle all of this is to have a > completely different compiler which defaults to a totally separate > /usr/include and /usr/lib area. i686-pc-mingw-gcc. Hmm. It has a nice > ring to it. Hmmm ... could it be because it makes perfect sense ;-? Seriously, this is what I used to recommend to anyone who'd ask for a "build environment" for Mingw. Glad to see I'm not the only one ... Regards, Mumit -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple