-
Notifications
You must be signed in to change notification settings - Fork 368
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't build network library on Windows #17
Comments
Comment by zenntenn @abailly I got passed this issue, sort of, but I'm still not able to compile test.c. When skipping it I can run idris2, but when I do the install for the libraries it's failing, as well as some of the (non-network) tests are failing for reasons I don't entirely understand. I have a branch on my repo for what I'm working on right here: https://github.com/zenntenn/Idris2/tree/MyConfigs-DontMerge It has some configs unique to my machine in there, as I don't really want to make a proper branch for PR purposes until I actually get it working on my machine. |
Comment by zenntenn @melted adding that to test.c does move things forward a bit #ifndef _WIN32
#include <netinet/in.h>
#include <arpa/inet.h>
#else
#include <winsock2.h>
#include <Ws2tcpip.h>
#endif but still fails later
|
Comment by arabelladonna Using this as a guide, I tried running |
Comment by arabelladonna Sorry for the late response. Here's the exact output:
|
Comment by arabelladonna Yeah, I had said in my original post that it was failing during linking due to |
Comment by abailly The thing is that's 2 different situations because there are 2 different |
Solved here. |
Issue by zenntenn
Saturday Aug 10, 2019 at 17:07 GMT
Originally opened as edwinb/Idris2-boot#78
Using Idris 1.3.2, and msys64, on Windows 10.
I was able to resolve the issues in https://github.com/edwinb/Idris2/issues/41, but now I'm getting stuck on the
make network
step, after completingmake idris2
,make prelude
andmake base
.Note: I do have netinet\in.h in my path, it's the first path entry even just to be sure.
Also, I added the -lws2_32 switch myself. Without it it fails earlier, with this error:
The text was updated successfully, but these errors were encountered: