Mail Archives: cygwin/2001/07/03/17:40:39
When I try to compile things with gcc 3.0 against <window.h>, the build
ends in a crash like so:
gcc -DHAVE_CONFIG_H -I. -I../../../swarm-2001-06-27/src/defobj -I../..
-I../.. -I../../libobjc -I../../../swarm-2001-06-27/libobjc -I..
-I../../../swarm-2001-06-27/src/defobj/..
-I../../../swarm-2001-06-27/src/defobj/../collections
-I../../../swarm-2001-06-27/src/defobj/../misc -I//c/jdk1.3.1/include
-I//c/jdk1.3.1/include/win32 -I../../avcall -DBUILDING_SWARM -g -O2
-Wall -Wno-import -Wno-protocol -Werror -Wno-unknown-pragmas
-Wno-unknown-pragmas -c -DDLL -DPIC
../../../swarm-2001-06-27/src/defobj/Arguments.m -o .libs/Arguments.lo
In file included from /usr/include/w32api/winnt.h:144,
from /usr/include/w32api/windef.h:145,
from /usr/include/w32api/windows.h:98,
from
../../../swarm-2001-06-27/src/defobj/Arguments.m:29:
/usr/include/w32api/basetsd.h:95: parse error before ',' token
This file basetsd.h in current cygwin has the following at lines 94 and
95:
typedef __int64 LONG64, *PLONG64;
typedef __int64 INT64, *PINT64;
Followed by
typedef unsigned __int64 ULONG64, *PULONG64;
typedef unsigned __int64 DWORD64, *PDWORD64;
If I comment lines 94-95, my programs compile, no trouble, and I stared
at your code a long time and started to think you would know how to fix
it, perhaps easily. I started to suspect there is some problem with the
typedef __int64 being used "bare", without a qualifier, such as "int" or
such. What do you think?
Can you include my (pauljohn AT ukans DOT edu) in your cc line, because I'm not
a member of this list (yet)
--
Paul E. Johnson email: pauljohn AT ukans DOT edu
Dept. of Political Science http://lark.cc.ukans.edu/~pauljohn
University of Kansas Office: (785) 864-9086
Lawrence, Kansas 66045 FAX: (785) 864-5700
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -