Still cannot update to 1.76

rustart · February 23, 2024, 5:00pm

info: syncing channel updates for 'stable-x86_64-pc-windows-msvc'
info: latest update on 2024-02-08, rust version 1.76.0 (07dca489a 2024-02-04) 
error: component 'rust-std' for target 'asmjs-unknown-emscripten' is unavailable for download for channel 'stable'
If you don't need the component, you could try a minimal installation with:

I have:
rustc 1.75.0 (82e1608df 2023-12-21)
rustup 1.26.0 (5af9b9484 2023-04-05

I do not know do I need the component 'rust-std' for target 'asmjs-unknown-emscripten' or do not.

jofas · February 23, 2024, 5:25pm

Looks to me like the asmjs-unknown-emscripten target got removed completely. I'll see if I can find the commit where it happened, but I just updated from 1.75.0 to 1.76.0 and when I ran rustup target list with 1.75.0 the asmjs-unknown-emscripten target was listed whereas for 1.76.0, it is not.

Edit: found the PR, wasn't hard:

Edit: The proposal for removing the target is hilarious:

github.com/rust-lang/compiler-team

Condemn `asmjs-unknown-emscripten` to push a boulder up a hill for eternity

opened 08:23AM - 26 Aug 23 UTC

closed 11:34AM - 02 Oct 23 UTC

workingjubilee

T-compiler major-change major-change-accepted

# Proposal I believe this is [the traditional punishment](https://en.wikipedi…a.org/wiki/Sisyphus) for those that [cheat Death and find Death catching up with them again](https://github.com/rust-lang/rust/issues/51856). The target support code will be ~~placed beyond the reach of mortal hands~~ removed, because it is [impossible to make the asmjs target functional again with any recent version of emscripten](https://github.com/emscripten-core/emscripten/issues/18013). # Mentors or Reviewers I recommend Thanatos, but any of the Chthonic gods will do. # Process The main points of the [Major Change Process][MCP] are as follows: * [x] File an issue describing the proposal. * [ ] A compiler team member or contributor who is knowledgeable in the area can **second** by writing `@rustbot second`. * Finding a "second" suffices for internal changes. If however, you are proposing a new public-facing feature, such as a `-C flag`, then full team check-off is required. * Compiler team members can initiate a check-off via `@rfcbot fcp merge` on either the MCP or the PR. * [ ] Once an MCP is seconded, the Final Comment Period begins. If no objections are raised after 10 days, the MCP is considered **approved**. You can read [more about Major Change Proposals on forge][MCP]. [MCP]: https://forge.rust-lang.org/compiler/mcp.html # Comments **This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.**

rustart · February 23, 2024, 5:46pm

So, I can use, cannot I ? :

rustup toolchain add stable --profile minimal

jofas · February 23, 2024, 5:58pm

I'd simply remove asmjs-unknown-emscripten with

rustup toolchain remove asmjs-unknown-emscripten

and then update normally with

rustup update

system · May 23, 2024, 5:58pm

This topic was automatically closed 90 days after the last reply. We invite you to open a new topic if you have further questions or comments.

Topic		Replies	Views
Still in the 1.75 version help	3	270	January 3, 2025
Trying to get wasm/asmjs stuff compiling	3	2645	January 12, 2023
Emscripten Error - Could not create LLVM TargetMachine help	3	4309	January 12, 2023
Should we downgrade / drop the asmjs target?	1	998	July 17, 2019
Unable to add thumbv7em-none-eabihf target embedded	2	493	July 29, 2024

Still cannot update to 1.76

Related topics