-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
emsdk install failing #6275
Comments
Yes I have the same problem but with emscripten-1.37.35 |
Similar problem. However, i was able to download the archive manually from the browser. Is there a way to bypass the download stage(maybe put the archive to a specific directory manually) and install directly? |
@jjyyxx Put the zip in the |
That's a good workaround, thanks! |
Thanks. It works perfectly |
This seems to have been caused by https://github.com/blog/2507-weak-cryptographic-standards-removed. The version of Python included in the Windows build is too old. Edit: It's because of the included version of OpenSSL is too old (i.e. less than 1.0.1). |
Sounds like we need to update the Python in the windows emsdk, but is this windows-only? The initial report here was on Mac. |
Yep I’m seeing this on macOS 10.12 and 10.13. |
Is the core issue the same, do those MacOS versions ship with too-old versions of python? |
Python version is 2.7.10 on both macOS versions I've tried, I guess that must be too old if that's the issue. |
Just updated to MacOS 10.13.3 and the install latest command worked! Adding some things I saw, which may or may not be helpful. |
kripken - yes it's an issue on windows too. I also got this error when trying to compile a project that worked fine in 1.35.00 urllib2.URLError: <urlopen error [Errno 1] _ssl.c:504: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version> |
Sorry, I missed that it was originally reported on macOS, as I had the same issue on Windows. It's actually the version of OpenSSL that's too old (version 1.0.1 or higher is needed for TLS 1.2). Python 2.7.5 for Windows includes OpenSSL 0.9.8y, and macOS 10.13.3 includes OpenSSL 0.9.8zh. |
Yep, I've retried on macOS 10.13 and it does seem to work so it's just 10.12 where I have the problem (Which is my main development machine). I'll use the workaround that was posted until I get round to upgrading. Thanks for the responses! |
I'm able to reproduce this on Windows. Thanks for troubleshooting versions in the above, very useful. Emsdk bundles the Portable Python package on Windows, and on other OSes depends on python being installed by default on the system. Unfortunately latest version of Portable Python seems to be 2.7.6.1, which by @Krelborn 's comment above seems to be too old, as 2.7.10 was detected to be too old. It looks like we need to source an up to date portable python installation. |
https://winpython.github.io/ looks promising, I'll see if we could migrate to using that. Although https://stackoverflow.com/questions/29472289/is-there-portable-python-2-7-windows-distribution-without-any-libraries-included suggests "I have to unpack 1.5GB first and uninstall unused packages." so not sure if this might cause a download size impact. |
FYI: According to the release notes on python.org, Python 2.7.7 on Windows includes OpenSSL 1.0.1g. Note that the version of Python shouldn't matter on macOS, as it is only on Windows that Python has its own copy of OpenSSL baked in. On other operating systems Python relies on the OpenSSL version that is installed in the system. |
A fix is now in emscripten-core/emsdk@4c8ea1b It would be great if someone can help trying this out:
should obtain Python 2.7.13.1 64-bit and Emscripten 1.37.35 precompiled. |
On macOS side, I'm thinking that we have no other easy option rather to call macOS 10.12 unsupported, and ask users to update to macOS 10.13? Or I wonder if manually downloading and replacing macOS bundled python with a newer python via homebrew or similar would work? |
Installing binaryen (#6276) works with Python 2 and 3 from Homebrew: $ python2 --version
Python 2.7.14
$ python3 --version
Python 3.6.4
$ python2 /usr/local/bin/emcc -s WASM=1 main.c #works
$ python3 /usr/local/bin/emcc -s WASM=1 main.c #works More permanent solution (bash): alias emcc="python2 /usr/local/bin/emcc" # or python3 |
Now Emscripten build requires OSX 10.13 (Xcode9.3beta) See emscripten-core/emscripten#6275
Now Emscripten build requires OSX 10.13 (Xcode9.3beta) See emscripten-core/emscripten#6275
I am trying to add SIMD support to our application and I get the following error: |
Has anyone had a chance to try @juj's steps a few comments back? #6275 (comment) I think we're waiting on that to move forward here. |
I can confirm that on windows 10 pro the python included in the emsdk-portable download was failing for me, after removing the python contents, I just replaced it with my own python 2.7 root and left the folder name as is, managed to download/install without issues. |
Emsdk updated to using Python 2.7.13.1 on Windows since this bug was originally reported, so it should be fixing the issue on Windows, although the problem is that if user has old Python on emsdk on Windows, they cannot use It's good to know that on macOS manually updating Python e.g. via brew will help. Unlike Windows, on macOS we don't bundle Python in emsdk because macOS comes with Python shipped, and we've been assuming that it would be a functional one. I'll close this bug as fixed - unfortunately a manual update of Python or redownload of emsdk may be needed for users, but once one has the latest version, the issue should not be present. |
Note that we currently do not link to an installer for windows, instead we recommend people get the emsdk and let it do the rest, like on other platforms. (Because I don't know how to build or test the installer...) |
installing |
Seems like emsdk is still using Python 2.7.5.3 and that it still has this issue. I just tried it today and installed Python 3.6.5 before because emsdk wouldn't even start otherwise. See emscripten-core/emsdk#140 |
The NSIS installer .exes on Windows were deprecated at some point, since it was not much gain to support an extra deployment workflow, and the Windows emsdk portable zip based package does much of the same thing with less hassle. The only thing that's different in the Windows emsdk portable zip package compared to macOS and Linux is that in the Windows package, we bundle portable Python 2.7.13.1 into the zip package. |
Oh hmm, I now see that the Downloads page at http://kripken.github.io/emscripten-site/docs/getting_started/downloads.html# no longer mentions a link to the downloadable zip packages. That is, to these zip files:
and indeed, in the above, I was not able to find the link to the Buildbot dashboard in my email inbox, could you link to that here? |
@juj do you mean this link? http://ec2-54-213-252-128.us-west-2.compute.amazonaws.com:8112/#/ I opened a PR on the emsdk repo to update the links there (to point to the website downloads docs), emscripten-core/emsdk#141 |
Just to add: I updated from Python 2.7.10 to 2.7.14 on macOS Sierra, and suddenly it fixed this issue. I updated with Macports: # install latest
sudo port install python27
# alias to 'python' command
sudo port select --set python python27 Quit and re-open terminal, then run |
Just curious: It's been a while since the documentation was changed requiring windows users to install python separately from emsdk (#6298). Is this now the official norm or still just a work around until bundling python into emsdk gets resolved? We haven't changed our CI yet to install python and don't want to put in the time if in a few weeks/months it's not going to matter. |
There are no current plans to improve the windows SDK install and bundle things like python - I'd love for us to, but unless someone volunteers, for now the best we can do is an experience similar to the other platforms. |
In MacOS ref:https://stackoverflow.com/questions/27835619/urllib-and-ssl-certificate-verify-failed-error |
Firstly,I typed "emsdk install latest" in git cmd,but it said "bash:git:command not found" |
macos 10.12.4 following your getting_started for 1.38.28. |
MacOS 10.14.5. Installed python from python.org. |
This worked for me (OSX huge headache) |
it works for me (OSX) |
Here is a bandage (not secure as you bypass cert checks) to fix it: edit emsdk.py change Make sure to add: |
This results in:
|
I am trying to update my emsdk installation and getting the following error after running
./emsdk install latest
.I'm seeing this whether I try to upgrade an existing installation or install from a clean copy of the SDK. Platform is macOS. I tried to install 1.37.33 as well and that failed with the same error. Is anyone else seeing this problem?
The text was updated successfully, but these errors were encountered: