Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-Id:	<5.0.1.4.2.20001202112731.02f2e368@192.168.200.41>
X-Sender:	rschulz AT 192 DOT 168 DOT 200 DOT 41
X-Mailer:	QUALCOMM Windows Eudora Version 5.0.1
Date:	Sat, 02 Dec 2000 12:15:28 -0800
To:	"Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>,
	"Andreas Eibach" <a DOT eibach AT gmx DOT net>, <cygwin AT sources DOT redhat DOT com>
From:	Randall R Schulz <rschulz AT teknowledge DOT com>
Subject:	Re: ARGH! Getting "'DWORD' undeclared ..." when buiilding from
	source - did I break something?
In-Reply-To:	<4.3.1.2.20001202141238.020ba000@pop.ma.ultranet.com>
Mime-Version:	1.0
X-MDaemon-Deliver-To:	cygwin AT sources DOT redhat DOT com
X-Return-Path:	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 AT rfk DOT com



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -