This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
RE: sockets and mingwin32
- To: "'JP Shipherd'" <jp at nuancecom dot com>
- Subject: RE: sockets and mingwin32
- From: Colin Peters <colin at bird dot fu dot is dot saga-u dot ac dot jp>
- Date: Wed, 5 Mar 1997 16:21:53 +0900
- Cc: "'GNU-Win32'" <gnu-win32 at cygnus dot com>
JP Shipherd[SMTP:jp@nuancecom.com] wrote:
>but the cygwin headers keep creeping in and I get errors like:
>
>C:\gnu32\H-i386-cygwin32\lib\gcc-lib\i386-cygwin32/cygnus-2.7.2-961023/../..
>/../
>../i386-cygwin32/include/sys/types.h:131: warning: `FD_SET' redefined
[snip]
>Is the i386-cygwin32/include path built into gcc (g++)? It's not in any of
>my include env vars:
>
>declare -x
>CPLUS_INCLUDE_PATH="/gnu32/mingw32/include:/gnu32/mingw32/include/non
>ansi:/gnu32/win32/include"
>declare -x
>C_INCLUDE_PATH="/gnu32/mingw32/include:/gnu32/mingw32/include/nonansi
>:/gnu32/win32/include"
Indeed yes, and I just found out about the problem today (sorry, I should
have been more careful in my testing). Anyway it seems that cpp at least
does know something about standard include file locations. Fortunately
you can work around this problem by adding "-iprefix /mingw32/include/"
or some such to the cpp options in the Mingw32 specs file (line 8)
so that it looks like this:
*cpp:
%{posix:-D_POSIX_SOURCE} -iprefix /mingw32/include/
This seems to take care of that problem (I hope). There may still be
problems with winsock and Mingw32, but at least you'll be getting the
right header files.
Colin.
-- Colin Peters - colin@bird.fu.is.saga-u.ac.jp
-- Saga University Dept. of Information Science
-- http://www.fu.is.saga-u.ac.jp/~colin/index.html
-- http://www.geocities.com/Tokyo/Towers/6162/
-
For help on using this list, send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".