Cygwin Problem

[Earnie Boyd]

Norman Vine wrote:
> 
> Jason Tishler writes:
> >
> >On Fri, Feb 09, 2001 at 10:06:05AM -0500, Norman Vine wrote:
> >> It seems as if the newest stuff does not -D_WIN32 like it used to.
> >>
> >> Chris warned that this would cause lot's of things to break.
> >>
> >> I had to add a -mwin32 to all the gcc flags to get Python to compile.
> >>
> >> I am not sure that this is the best way because -mwin32 may do more
> >> then we want.  -mwin32 is also only in the latest gcc ( 2.95.2.7 )
> >>
> >> Any suggestions
> >
> >Unfortunately, I believe that the right solution is to do as Chuck did
> >in the following (see the first paragraph):
> >
> >    http://sources.redhat.com/ml/cygwin/2001-02/msg00244.html
> >
> 
> I do not think that this is the same problem
> Hopefully this dumb example will illustrate my point better
> 
> Cheers
> 
> Norman Vine
> 
> /* jnk.c -- -mwin32 switch test
> $ gcc -DWIN32 jnk.c
> jnk.c:1: windows.h: No such file or directory
> 
> $ gcc -mwindows jnk.c
> jnk.c:1: windows.h: No such file or directory
> 
> $ gcc -mwin32 jnk.c
> $ a
> A dumb test
> */
> 
> #include <windows.h>
> 
> int main(int argc, char **argv)
> {
>         printf("A dumb test\n");
>         return 0;
> }

I haven't tried building python recently so I don't know how this
relates but with gcc-2.95.2-7 you must either -mwin32 or
-I/usr/include/w32api for GCC to find the windows.h file.

Earnie.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com