Re: ARGH! Getting "'DWORD' undeclared ..." when buiilding from source - did I break something?

[Randall R Schulz <rschulz at teknowledge dot com>]

Larry,

That's curious.

Here's the complete contents of "/usr/include/windef.h" in my recent clean 
Cygwin 1.1.6 install (with all updates currently mirrored on 
Sunsite.utk.edu installed):

-==-
#include <w32api/windef.h>
-==-

However, the exact typedef you quote appears on line 120 of 
"/usr/include/w32api/windef.h", the ultimate target of this #include. That 
typedef is the first line of content actually passed by the pre-processor 
to the compiler as a result of a #include of "/usr/include/windef.h" (that 
observation is based on running "gcc -E /usr/include/windef.h").

Randall Schulz
Teknowledge Corp.
Palo Alto, CA USA


At 11:12 12/2/2000, Larry Hall (RFK Partners, Inc) wrote:
>...
>
>Perhaps someone can help me understand why people are having these kinds of
>problems.  I find DWORD defined as:
>
>typedef unsigned long DWORD;
>
>in /usr/include/windef.h.
>
>This file comes from the w32api package (yes, this time I took the time to
>go find the definition and track the file to its package myself!;-))  Are
>questions like these popping up just because people aren't installing all
>the packages (but still expecting everything to work fine!;-)) or is there
>some other reason I don't understand that accounts for problems like this?
>
>Larry Hall                              lhall@rfk.com



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com