This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: [pauljohn@ukans.edu: I believe this is a typo.]
- To: Christopher Faylor <cgf at redhat dot com>
- Subject: Re: [pauljohn@ukans.edu: I believe this is a typo.]
- From: Earnie Boyd <earnie_boyd at yahoo dot com>
- Date: Tue, 07 Aug 2001 06:39:30 -0600
- CC: cygwin-developers at cygwin dot com, MD List <MinGW-Dvlpr at SF dot Net>
- References: <20010807002110.H25338@redhat.com>
- Reply-To: CD List <Cygwin-Developers at Cygwin dot Com>, MD List <MinGW-Dvlpr at SF dot Net>
Mumit or Danny,
Is this just gcc-3.0 issues?
Earnie.
Christopher Faylor wrote:
>
> 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 <pauljohn@ukans.edu> -----
>
> From: Paul Johnson <pauljohn@ukans.edu>
> To: cygwin@cygwin.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 <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@ukans.edu) in your cc line, because I'm not
> a member of this list (yet)
>
> --
> Paul E. Johnson email: pauljohn@ukans.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 -----
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com