-
Notifications
You must be signed in to change notification settings - Fork 710
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
Node 16 #947
Comments
Sadly we have some reasons to stick with (or at least to continue to support) an older version node, at least for our internal tooling. See #877. I agree it would be nice one to upgrade. In the mean time the issue you are facing with You are also free to install whatever version of node you like of course, and configure via the |
Thanks for your answer. I understand you cannot upgrade yet. NODE_OPTIONS is a nodejs environment variable. The problem I have is that it is not possible to add arguments directly to NODE_JS because emcc assumes it is only a path to an executable (see here). The PR you linked seems to be CMake-specific? |
Considering that you cannot upgrade my best solution is probably to change NODE_JS to a different node version. I'm closing this issue for now. |
…0240930.1 (emscripten-core#947) Microsoft.NETCore.Runtime.Wasm.Emscripten.Transport From Version 9.0.0-alpha.1.24473.1 -> To Version 9.0.0-alpha.1.24480.1 Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
The current node version installed with the SDK is node 14. Compiling a library with pthread support using tools like
emconfigure
andemmake
might fail because the configuration script cannot run the compiled binaries. Node 14 requires the flag--experimental-wasm-threads
for that which cannot be passed usingNODE_OPTIONS
. The following warning appears in the output:Node 16 is the current LTS version of node and does not require this flag. Adding Node 16 support to emsdk should solve this problem.
The text was updated successfully, but these errors were encountered: