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 sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <20000614150416.19670.qmail@web108.yahoomail.com> Date: Wed, 14 Jun 2000 08:04:16 -0700 (PDT) From: Earnie Boyd Reply-To: earnie_boyd AT yahoo DOT com Subject: Re: Is -mno-cygwin support being removed???? (What th'?) To: cygwin AT sourceware DOT cygnus DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii --- Chris Faylor wrote: > If I am understanding this correctly, it sounds like there is a newer > version of mingw which should be merged back into the cygwin > distribution. Either that or I should just rip out all of this mingw > stuff and let the mingw maintainers deal with the problem. > Cool down Chris. The problem here that Dale has rightly corrected, IMHO, is that the -mno-cygwin switch is pulling in header files from the Cygwin/usr/include directory and thus requiring the cygwin1.dll. There has always been a MinGW distribution since the introduction of the -mno-cygwin switch and I know that you're aware of that, however the -mno-cygwin switch was meant to allow the Cygwin GCC to build executables without the need for the cygwin1.dll. I myself choose to use the MinGW GCC to build Windows Native Applications (WNA) instead of the -mno-cygwin switch because of the reasons that has caused this discussion. It has always been my belief that the -mno-cygwin switch should be treated more as a cross-compile which Dale has given instructions to setup. Regards, ===== --- Earnie Boyd: __Cygwin: POSIX on Windows__ Cygwin Newbies: __Minimalist GNU for Windows__ Mingw32 List: Mingw Home: __________________________________________________ Do You Yahoo!? Yahoo! Photos -- now, 100 FREE prints! http://photos.yahoo.com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com