Game Release Info:.:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::..:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::..:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::..:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::..::::::::::.......:::::::::..:::::::::` ````` `::::::::..::::::::: `.-:::::::::.`::::::::..::::::::: `-:::::::::::::---:-`::::::::..::::::::: `-::::::::::::. Invizimals shadow zone psp cso.

I was just trying to build netcat in MSYS using MinGW and realized that MinGW never really ported all of the BSD socket stuff to Windows (eg sys/socket.h). I know you can use Windows Sockets in MinGW, but why did they never make a Windows port of the BSD sockets? I noticed quite a few programs using #ifdef's to workaround the issue.

O.S., Thank you for the information and pointing me in the right direction. >>From: Ozkan Sezer Subject: Re: [Mingw-w64-public] Application build failure To: mingw-w64-public@. On 8/29/13, wynfield@. Wrote: > > I am working on building the Crypt_SSLeay library package on MinGw.

The > build fails with the following error message. It looks like I'm missing a > file called in.h which should be in directory /include/netinet. > > There is no directory netinet and of course no in.h which should be in it. > > Does anyone have experience building Crypt_SSLeay on MinGW/Msys or can you > point me in the direction of what I need to do to get./netinet/in.h? > > Any assistance is appreciated. > > > --- imported error text > gcc -c -DPERL_USE_SAFE_PUTENV -DDEBUGGING -fno-strict-aliasing -pipe > -Wdeclaration-after-statement -DUSEIMPORTLIB -O3 -fno-unit-at-a-time -s > -mtune=pentium -DVERSION= '0.64 ' -DXS_VERSION= '0.64 ' > '-I/usr/lib/perl5/5.8/msys/CORE' SSLeay.c > In file included from SSLeay.xs:13:0: > C:/MinGW/msys/1.0/lib/perl5/5.8/msys/CORE/perl.h:925:27: Fatal error: > netinet/in.h: No such file or directory > Compile aborted > make: *** [SSLeay.o] Error 1 netinet/in.h is a bsd sockets header. You possibly misconfigured that software, or its configury is broken when targeting windows.

O.S., Thank you for the information and pointing me in the right direction. >>From: Ozkan Sezer Subject: Re: [Mingw-w64-public] Application build failure To: mingw-w64-public@. On 8/29/13, wynfield@. Wrote: > > I am working on building the Crypt_SSLeay library package on MinGw.

The > build fails with the following error message. It looks like I'm missing a > file called in.h which should be in directory /include/netinet. > > There is no directory netinet and of course no in.h which should be in it. > > Does anyone have experience building Crypt_SSLeay on MinGW/Msys or can you > point me in the direction of what I need to do to get./netinet/in.h? > > Any assistance is appreciated. > > > --- imported error text > gcc -c -DPERL_USE_SAFE_PUTENV -DDEBUGGING -fno-strict-aliasing -pipe > -Wdeclaration-after-statement -DUSEIMPORTLIB -O3 -fno-unit-at-a-time -s > -mtune=pentium -DVERSION= '0.64 ' -DXS_VERSION= '0.64 ' > '-I/usr/lib/perl5/5.8/msys/CORE' SSLeay.c > In file included from SSLeay.xs:13:0: > C:/MinGW/msys/1.0/lib/perl5/5.8/msys/CORE/perl.h:925:27: Fatal error: > netinet/in.h: No such file or directory > Compile aborted > make: *** [SSLeay.o] Error 1 netinet/in.h is a bsd sockets header.

You possibly misconfigured that software, or its configury is broken when targeting windows. >From: JonY >Date: Thu, 29 Aug 2013 22:00:12 +0800 >Subject: Re: [Mingw-w64-public] Application build failure >> On 8/29/2013 20:41, wynfield wrote: >> >> I am working on building the Crypt_SSLeay library package on MinGw.

The build fails with the following error message. It looks like I'm missing a file called in.h which should be in directory /include/netinet.

>> >> There is no directory netinet and of course no in.h which should be in it. >> >> Does anyone have experience building Crypt_SSLeay on MinGW/Msys or can you point me in the direction of what I need to do to get./netinet/in.h? >> >> Any assistance is appreciated. >> > This file was never part of mingw-w64, use Cygwin if you must use Unix API. A file or package does not have to be a part of mingw. It's my understanding that the very point of MinGW is to enable the building of programs which will run on various Miscrosft Windows O.S.' S and libraries.

Data protector software encryption. BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 13:44, JonY wrote: > On 8/30/2013 09:02, wynfield wrote: >> >>> This file was never part of mingw-w64, use Cygwin if you must use Unix API. >> >> A file or package does not have to be a part of mingw. It's my understanding that the very point of MinGW is to enable the building of programs which will run on various Miscrosft Windows O.S.'

S and libraries. > > *Nix socket APIs were never part of Windows, so your program was never > designed on run on Windows, mingw or not. > > Use Cygwin if you need *Nix API. To be precise: Your program was never meant to run on W32.