On Sun, Mar 18, 2001 at 09:34:11AM +1100, Robert Collins wrote: >No objections either way. The autoconf macro will probably be useful >anyway if someone contributes the logic for WINE to it... > >I've never had a problem with conflicts between w32api and the unix >files, and adding the appropriate logic to tell the difference between >native win32 and cygwin seems like a necessary step for a reliable port >any IMO. I forgot to mention that -mno-win32 will still "do the right thing". It will remove -I/usr/include/w32api entirely -- for the purists among us. cgf
- gcc 2.95.3-1 and -mwin32 Christopher Faylor
- Re: gcc 2.95.3-1 and -mwin32 Robert Collins
- Re: gcc 2.95.3-1 and -mwin32 Christopher Faylor
- Re: gcc 2.95.3-1 and -mwin32 Robert Collins
- Re: gcc 2.95.3-1 and -mwin32 Charles S. Wilson
- Re: gcc 2.95.3-1 and -mwin32 Christopher Faylor
- Re: gcc 2.95.3-1 and -mwin32 Robert Collins
- Re: gcc 2.95.3-1 and -mwin32 Charles S. Wilson
- RE: gcc 2.95.3-1 and -mwin32 Norman Vine
- Re: gcc 2.95.3-1 and -mwin32 Trevor Forbes
- Re: gcc 2.95.3-1 and -mwin32 Robert Collins
- Re: gcc 2.95.3-1 and -mwin32 Christopher Faylor
- Re: gcc 2.95.3-1 and -mwin32 Robert Collins
