-
Notifications
You must be signed in to change notification settings - Fork 194
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
Windows 10, simple hello world program fails #1921
Comments
This looks very similar to scikit-image/scikit-image#3226 (comment) |
OK, I was able to fix the issue. The problem arises form the fact that by default, clang-cl.exe is the 32 bit version (or at least, was on my system). If I change my path so the default clang-cl.exe is the 64 bit version, compilation and linking run without any problem.
I think this should probably be added to the documentation somewhere, right? |
@jeanlaroche I would be very happy if you updated the documentation, yes ;-) |
@serge-sans-paille I solved this issue by defining full path to clang-cl.exe in the file .pythranrc but had to use short legacy names to avoid spaces in the path:
I tried to use both types of quotes for the usual long path, but generated call was not valid. |
@AndrewUshakov hell that's ugly :-) We should support quote there as we already did in 7fc75bb . I'll implement that. |
@AndrewUshakov on Linux, just the anme with spaces and no quotes works fine. Are you telling me that
doesn't work? |
@serge-sans-paille If use quotes, output to console looks like: Without quotes, all is Ok, Sorry. Probably I did something wrong yesterday. |
Where in the doc should I add that? I tried to find mentions of windows in docs, but couldn't find anything. Simply in MANUAL.rst? |
An update on this. With the latest version of pythran. On windows10, pythran uses clang-cl by default, which is good. But the linker it uses is still
which I don't think is right. I'm getting lots of linking errors as a result. |
Windows10, trying to compile with pythran:
https://pastebin.com/EzRQJAAK
The text was updated successfully, but these errors were encountered: