`rustup default` doesn't show proper warning when architecture is not compatible

[bombless]

Fresh install rustup on my Windows Subsystem for Linux, choose stable-x86_64-apple-darwin toolchain
after installation, run rustc it reports ~/.rustup/toolchains/stable-x86_64-apple-darwin/bin/rustc: 1: Syntax error: "(" unexpected

Or if you choose stable-x86_64-pc-windows-gnu, run rustc after installation,
it reports error: the 'rustc' binary, normally provided by the 'rustc' component, is not applicable to the 'stable-x86_64-pc-windows-gnu' toolchain

[ehuss]

I think there may be some confusion here. There are two concepts in rustup, the toolchain host, and the standard library targets. It looks like you may have installed toolchains for other hosts, which won't run. You only need to install the toolchain for the host you are running on (so on WSL, it would be stable-x86_64-unknown-linux-gnu). To cross compile, you only need to install the standard library target (rustup target add x86_64-pc-windows-gnu). There is more information at https://rust-lang.github.io/rustup/cross-compilation.html about how to install targets, and https://rust-lang.github.io/rustup/concepts/index.html for more on the different concepts in rustup.

Just beware that cross compiling from linux to windows or macos is not particularly easy. This recent blogpost contains an overview of how to cross-compile to windows.

[bombless]

Thank you! I'll have a try a few hours later when I can reach my machine.

[bombless]

rustup run nightly-x86_64-unknown-linux-gnu cargo run --target=x86_64-pc-windows-gnu seems to do the job.

But I still wonder if it is considerable that we change rustup default a little bit so it can warn incompatible architecture

[workingjubilee]

That would be a rustup bug. Could this issue be transferred?

[ChrisDenton]

Attempting to transferr to rust-lang/rustup since this is an issue with the rustup tool...

@rustbot transfer rustup