Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Tue, 7 Aug 2001 00:21:10 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: [pauljohn AT ukans DOT edu: I believe this is a typo.] Message-ID: <20010807002110.H25338@redhat.com> Mail-Followup-To: cygwin-developers AT cygwin DOT com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i This is an old problem that I never saw any reaction to. Does anyone understand what the problem may be here? cgf ----- Forwarded message from Paul Johnson ----- From: Paul Johnson To: cygwin AT cygwin DOT com Subject: I believe this is a typo. Date: Tue, 03 Jul 2001 16:22:30 -0500 When I try to compile things with gcc 3.0 against , 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/ ----- End forwarded message -----