-
Notifications
You must be signed in to change notification settings - Fork 3.4k
emsdk_env.sh racy #9090
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
Comments
vargaz
added a commit
to vargaz/emsdk
that referenced
this issue
Jul 26, 2019
kripken
pushed a commit
to emscripten-core/emsdk
that referenced
this issue
Jul 26, 2019
sbc100
added a commit
to emscripten-core/emsdk
that referenced
this issue
Jul 9, 2020
This is an alternative fix for emscripten-core/emscripten#9090 which recently came up again after #539. Tested with bash, tcsh and fish.
sbc100
added a commit
to emscripten-core/emsdk
that referenced
this issue
Jul 9, 2020
This is an alternative fix for emscripten-core/emscripten#9090 which recently came up again after #539. Tested with bash, tcsh and fish.
sbc100
added a commit
to emscripten-core/emsdk
that referenced
this issue
Jul 11, 2020
This is an alternative fix for emscripten-core/emscripten#9090 which recently came up again after #539. Tested with bash, tcsh and fish.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
emsdk_env.sh calls emsdk construct_env which deletes the output file before creating the new one. If multiple copies of this script are ran in parallel in multiple shells, one copy could delete the file the other one is trying to source leading to errors like:
-bash: ./emsdk_set_env.sh: No such file or directory
The text was updated successfully, but these errors were encountered: