Open sargunv opened 8 years ago
I guess this happens with all Linux x64 binaries compiled with a recent version of GHC.
For now I don't own a Windows machine, but @simnalamburt any chance you can try WSL?
I do have a Windows 10 machine to test it but I'm afraid that I don't have enough spare time to debug. :cry:
Maybe I'll be able to try it at upcoming next weekend; May 13rd.
I just made some WSL environment, and I just found out that current WSL implementation cannot even run the stack
binary properly.
sudo apt-get update && sudo apt-get install stack -y
stack
# timer_create: Function not implemented
There's no possible way to debug it if I cannot even compile it. This is not a issue with Chips so please file the issue to the BashOnWindows issue tracker.
@kinoru Closing?
It's already been reported there, I mentioned that in the OP. Regardless, I think it should stay open here until it's resolved. Your choice though.
@sargunster It seems your description in the OP is correct. Thanks.
@simnalamburt Thank you for confirming the problem. By the way, I have a feeling that, even if WSL shipped with a complete set of Linux syscalls, somehow Chips would still not work.
I do not strongly object closing this issue, but my personal preference is to leave it open, as newcomers would normally check the list of open issues before they file a new one.
Oh, I wish I could be as cool as yyuu.
I recently started to use WSL, so I'm trying to resolve this issue now. Looks like WSL now does support the haskell, but I still receive this error message.
Failed to execute process './chips'. Reason:
exec: Exec format error
The file './chips' is marked as an executable but could not be run by the operating system.
I suspect the UPX, but not sure. I'll comment if I get some updates.
Windows Subsystem for Linux should be compatible with unmodified Linux executables, but Chips doesn't work:
Additionally, install from source doesn't work due to this WSL bug: https://github.com/Microsoft/BashOnWindows/issues/307