-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Fix emcc failure for wasm32. #73213
Fix emcc failure for wasm32. #73213
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
@bors r+ p=1 |
📌 Commit cd02052 has been approved by |
🌲 The tree is currently closed for pull requests below priority 1000, this pull request will be tested once the tree is reopened |
@bors p=1000 |
⌛ Testing commit cd02052 with merge 0f6aa648428adfe886c188c9a9e54ed2ec7caa3e... |
💥 Test timed out |
@bors retry |
closing tree as a precaution @bors treeclosed=1000 |
what did i miss lol @bors treeclosed=1000 |
☀️ Test successful - checks-azure |
@bors treeclosed- |
Accepting for beta backport as well as it's "just necessary" |
…-morse,Mark-Simulacrum [beta] backport This is a beta backport rollup of the following: * [beta] Revert heterogeneous SocketAddr PartialEq impls rust-lang#73318 * Fix emcc failure for wasm32. rust-lang#73213 * Revert rust-lang#71956 rust-lang#73153 * [beta] Update cargo rust-lang#73141 * Minor: off-by-one error in RELEASES.md rust-lang#72914 * normalize adt fields during structural match checking rust-lang#72897 * Revert pr 71840 rust-lang#72989 * rust-lang/cargo#8361 * e658200 from rust-lang#72901 r? @ghost
The wasm32 job is currently failing on CI with the error
ERROR: llc executable not found at /usr/bin/llc
. The issue is that emscripten-core/emsdk#472 has changed how emsdk discovers its configuration. We were relying on the global behavior that would use a configuration from the home directory. However, it looks like emsdk is moving away from that approach. This change adds the necessary env var for emcc to find the correct configuration.There are a few alternate approaches this could take. The
--no-embedded
option could be passed toemsdk activate
to use the old behavior, but it seems like they want to move away from that. Another option is to sourceemsdk_env.sh
, which is how these env vars normally get set. I'm not entirely sure how to do that easily in a Dockerfile, though.