Mirror of forum.nim-lang.org

3489 :: Windows: "import posix" => 'arpa/inet.h': No such file or directory

[2018-01-19T20:23:24+01:00]

monster (orginal) [2018-01-19T20:23:24+01:00] view original
Hi,

I'm trying to use the posix module, because I need htonl() and ntohl(), but if I import posix (Windows, vcc), I get this error message:
```
asyncnetcodetest.c(11): fatal error C1083: Cannot open include file: 'arpa/inet.h': No such file or directory
```
Can I fix this somehow?

Demos (orginal) [2018-01-19T21:30:48+01:00] view original

Windows isn't POSIX and thus that module does not work on windows.

the nativesockets has htonl and ntohl.

cheatfate (orginal) [2018-01-19T23:39:18+01:00] view original
```
import nativesockets
```
which is cross-platform and has ntohl/htonl declarations. Also github search in project for htonl/ntohl or any other procedure can help you in future.

monster (orginal) [2018-01-20T13:35:43+01:00] view original

There was not comment in the module documentation saying it's not available on Windows. If Windows is not POSIX compliant, shouldn'd the "import posix" fail on Windows? Or does it "partially" work on Windows? (AFAIK, Windows does support some of POSIX)

mashingan (orginal) [2018-01-20T17:15:02+01:00] view original

The first line of posix module paragraph mentions: This is a raw POSIX interface module. So it's obvious a simple ffi for native posix apis.

Also from the module name should be obvious though, on Windows using winlean and unix/linux using posix module

Demos (orginal) [2018-01-25T23:24:11+01:00] view original

Also some versions of windows are actually somewhat posix compliant, although not in very useful ways

xomachine (orginal) [2018-01-26T16:17:41+01:00] view original

shouldn'd the "import posix" fail on Windows?
No it should not. The posix module is very useful for building custom library wrappers for WINE (which is being compiled with --os:windows via winegcc under linux). So the posix module allows to access underlying linux interfaces.