Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Message-ID: <3DD3EB49.6000306@netscape.net> Date: Thu, 14 Nov 2002 13:28:25 -0500 From: Nicholas Wourms User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cygwin-developers AT sources DOT redhat DOT com Subject: Re: Fwd: Re: later w32api package required to build cygwin References: <3DD3E347 DOT 60703 AT yahoo DOT com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Earnie Boyd wrote: > Why isn't the cygwin build process using the winsup/w32api directory? > > > ------------------------------------------------------------------------ > > Message-ID: <005f01c28bf4$78c172a0$78d96f83 AT pomello> > From: "Max Bowsher" > To: > Subject: Re: later w32api package required to build cygwin > Date: Thu, 14 Nov 2002 15:42:43 -0000 > MIME-Version: 1.0 > Content-Type: text/plain; > charset="iso-8859-1" > Content-Transfer-Encoding: 7bit > > David Starks-Browning wrote: > > >>I've been attempting to build cygwin1.dll from within Cygwin. > > >>It fails because my installed /usr/include/w32api/winioctl.h (from the >>w32api-2.0-1 package) is out of date compared to that in cvs >>(winsup/w32api/include/winioctl.h). > > > Bug report from me: > http://sources.redhat.com/ml/cygwin/2002-10/msg01532.html > > I got no response. As I said in that message, I think it is a bug in gcc. > IIRC, the new gcc has started to ignore system directory overrides (in addition to barfing out that stupid message). Using -isystem instead of -I for including the local w32api dir might be the solution here, although I was just lazy and copied the header over to the system dir. Cheers, Nicholas