Date: Thu, 3 Mar 2011 12:37:37 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: w32api/include/winbase.h rev. 1.101, OVERLAPPED and -std=c99
Message-ID: <20110303173737.GA16585@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <4D6FC5BE.7030601@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4D6FC5BE.7030601@gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Thu, Mar 03, 2011 at 04:45:50PM +0000, Pete Batard wrote:
>Any application compiled in C99 mode and using OVERLAPPED is therefore 
>expected to break, and we have seen that issue after people upgraded 
>their cygwin installation and tried recompiling libusb [2]. Our current 
>workaround is to switch to gnu99, but with a source that is common to 
>both MSVC, MinGW and cygwin, GNU extensions is something we would like 
>to avoid. Also, the problem seems to have now spread to the latest 
>MinGW32 now (are they reusing cygwin's winbase.h?).

It's the other way around.  Cygwin's winbase.h comes from MinGW.  If
there is an issue you need to take it up with the MingW folks.

OTOH, for Cygwin programs you shouldn't be using winbase.h at all.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple