rustup: toolchain '$toolchain' may not be able to run on this system UX is not working well

Wanting to use musl instead of gnu, I run into this issue:

$ rustup toolchain add stable-x86_64-unknown-linux-musl
warning: toolchain 'stable-x86_64-unknown-linux-musl' may not be able to run on this system.
warning: If you meant to build software to target that platform, perhaps try `rustup target add x86_64-unknown-linux-musl` instead?
info: syncing channel updates for 'stable-x86_64-unknown-linux-musl'

  stable-x86_64-unknown-linux-musl unchanged - (error reading rustc version)

Notes

$ rustup --version
rustup 1.23.1 (2020-12-18)
info: This is the version for the rustup toolchain manager, not the rustc compiler.
info: The currently active `rustc` version is `(error reading rustc version)`

$ rustup show
Default host: x86_64-unknown-linux-gnu
rustup home:  /home/folaht/.rustup

installed toolchains
--------------------

stable-x86_64-unknown-linux-gnu
stable-x86_64-unknown-linux-musl (default)

active toolchain
----------------

stable-x86_64-unknown-linux-musl (default)
(error reading rustc version)

About this issue

Original URL
State: open
Created 3 years ago
Comments: 16 (15 by maintainers)

Commits related to this issue

Begin fixing #2672 We need a two-step process for this. Step 1 is to announce the deprecation of no-force options on update/install of toolchains and accept --force. Step 2, in the next release, is t... — committed to rbtcollins/rustup.rs by rbtcollins 3 years ago
Begin fixing #2672 We need a two-step process for this. Step 1 is to announce the deprecation of no-force options on update/install of toolchains and accept --force. Step 2, in the next release, is t... — committed to rbtcollins/rustup.rs by rbtcollins 3 years ago
Begin fixing #2672 We need a two-step process for this. Step 1 is to announce the deprecation of no-force options on update/install of toolchains and accept --force. Step 2, in the next release, is t... — committed to rbtcollins/rustup.rs by rbtcollins 3 years ago
Begin fixing #2672 We need a two-step process for this. Step 1 is to announce the deprecation of no-force options on update/install of toolchains and accept --force. Step 2, in the next release, is t... — committed to rbtcollins/rustup.rs by rbtcollins 3 years ago
Begin fixing #2672 We need a two-step process for this. Step 1 is to announce the deprecation of no-force options on update/install of toolchains and accept --force. Step 2, in the next release, is t... — committed to rbtcollins/rustup.rs by rbtcollins 3 years ago

Most upvoted comments

The question really is how many will be in 3 vs 1 or 2, and what can we do to maximise the size of bucket 3. Rustc itself has been super successful at this strategy of helpful, meaningful error messages, so I think we have significant prior art around the idea of taking this approach.

Observationally, given the problem is not reading the messaging, and a large number of people do express confusion about rustc’s messaging even when it is solved by reading the error message, we should definitely appreciate those details and not expect this to be completely solved, either way.

workingjubilee on Apr 17, 2021