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 Date: Wed, 7 Mar 2001 16:12:14 -0500 From: Christopher Faylor To: autoconf AT gnu DOT org Cc: cygwin AT cygwin DOT com Subject: Detecting the need for -mwin32 in newer cygwin gcc's Message-ID: <20010307161214.A20717@redhat.com> Mail-Followup-To: autoconf AT gnu DOT org, cygwin AT cygwin DOT com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i We've made a change in the newest version of cygwin that stops the Windows headers from being searched unless a -mwin32 option is specified on the gcc command line. This option also causes Windows options like "WIN32" to be defined automatically. We've done this to make porting easier for some programs which already have a Windows-specific port that is not appropriate when compiled under Cygwin. However, this causes problems for programs that still need to explicitly use Windows include files. Someone on the cygwin mailing list suggested that this calls for an autoconf option so that checking for this behavior can be added to configure. Basically, I think we need something like a AC_PROG_GCC_USES_MWIN32. Does this sound like a good way to go with this? Does anyone want to volunteer to implement this, if so? cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple