This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Using -mno-cygwin flag

Brian Salter-Duke wrote:

> Beginning the DDI compilation at Wed May 4 18:09:43 AUSCST 2005
> Compiling common object: soc_create.o
> gcc -DLINUX -O3 -mno-cygwin -fstrict-aliasing -I./include -DDDI_SOC -DMAX_SMP_PROCS=8 -DMAX_NODES=32 -c ./src/soc_create.c -o ./obj/soc_create.o
> In file included from src/soc_create.c:21:
> include/mysystem.h:34:28: sys/resource.h: No such file or directory
> include/mysystem.h:73:23: pthread.h: No such file or directory
> include/mysystem.h:81:21: netdb.h: No such file or directory
> include/mysystem.h:82:26: sys/socket.h: No such file or directory
> include/mysystem.h:83:26: netinet/in.h: No such file or directory
> include/mysystem.h:84:27: netinet/tcp.h: No such file or directory

This is working just the way it's supposed to.  I don't think you fully
understand what the -mno-cygwin flag means.  Cygwin provides the
unix/posix emulation layer, things like the berkeley sockets API and
pthreads[*] that you are missing above.  When you use -mno-cygwin, you
are using a completely different compiler.  Mingw has no emulation
layer, that's the "minimalist" part.  When you use mingw, you get a
standard C runtime library (provided by MSVCRT, i.e. Windows), the bare
win32 API, and not much else.  No berkeley sockets.  No pthreads.  None
of the stuff that Cygwin provides.

-mno-cygwin does not just "make things that doesn't depend on the cygwin
DLL", it removes Cygwin from the equation entirely.


[*] Yes I know of projects like pthreads-win32.  But that's neither
Cygwin nor mingw, really.

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]