rustup doesn't install a toolchain? about rustup

[casesolved-co-uk]

Does this have something to do with me using i686 as opposed to x86_64?

[casesolved-co-uk]

It was, fixed with the following on MacOS 10.11 (1.73.0 appears to be the latest compatible version):

rustup --verbose toolchain install 1.73.0-x86_64-apple-darwin
rustup default 1.73.0-x86_64-apple-darwin

[rbtcollins]

Hi, I think there might be a bug here.

Can you ls -ld /Users/rich/.rustup/toolchains/stable-i686-apple-darwin please?

[casesolved-co-uk]

There isn't one, rustup wouldn't create it. I think because i686 builds don't exist anymore possibly? So it was looking for v1.77 ?

[rami3l]

There isn't one, rustup wouldn't create it. I think because i686 builds don't exist anymore possibly? So it was looking for v1.77 ?

@casesolved-co-uk Looking at https://doc.rust-lang.org/nightly/rustc/platform-support.html#tier-3 i686-apple-darwin is a tier 3 target, so there's no guarantee that its artifacts will be available on the release server (that target corresponds to Core Solo/Duo Macs no later than mid 2006, so a bit less than two decades ago, are you sure that's what you wanted?). OTOH x86_64-apple-darwin is a perfectly fine tier 1 target.

@rbtcollins Where do you think Rustup's behavior could be improved in this case?

[rbtcollins]

@rami3l / @casesolved-co-uk

So there are a few possibilities.

I think rustup show does nothing with the distribution channels, so whether or not the target is supported or current is quite irrelevant.

The path in the error is where a toolchain dir is expected to be found.

So if there is no path on disk present, we need to ask why rustup was trying to access/examine one.

One possibility is that when the default toolchain is set to one that does not exist, rustup does not handle the toolchain not existing. This is a possible regression from my refactoring of toolchain structs recently. I think this is most likely.

Another possibility is that there was a path present, that was not a directory, but its been removed in the intervening time. I think this is less likely.

In terms of improvements, I rather suspect rustup should handle the case (if it is what I suspect) and show something like 'default toolchain (name) [not installed]'

[casesolved-co-uk]

Some additional info in case it helps:

I used the latest i686 version of rustup-init since it is the only one that would run on my Mac, hence why it was trying to install the i686 toolchain. Maybe the i686 init hasn't been updated?

Every attempt gave the same result: it refused to create a toolchains directory or the actual toolchain until I gave it a different target platform: x86_64.

It was a fresh install, I've never used/installed rust before, so no changes in paths.

My comment was based on the logic that maybe the only way that both up to date and not installed could both be true is if the stable version it is looking for doesn't exist?

I just wanted any working version of rustc to be installed because a python library wouldn't install without it.

[rami3l]

One possibility is that when the default toolchain is set to one that does not exist, rustup does not handle the toolchain not existing. This is a possible regression from my refactoring of toolchain structs recently. I think this is most likely.

@rbtcollins Please note that this is rustup 1.21.1 :: 1.21.0+13 (03e2c55 2019-12-20) and I'm not sure if the issue is still there after like 4 years... Anyway it definitely has nothing to do with your recent refactoring given that.

[rami3l]

@casesolved-co-uk If you're using an x86_64 Mac maybe you can try our latest test build targeting macOS 10.12: #3708 (comment)

If that doesn't work my recommendation is to try older x86_64 Rustup builds, probably something like v1.26.0. According to https://blog.rust-lang.org/2023/09/25/Increasing-Apple-Version-Requirements.html, Rust only supports macOS 10.12+ now.

Due to our release model it's not very feasible for us to pinpoint problems in an old build from 2019, sorry 🙇‍♀️

[casesolved-co-uk]

Yeah it's all moot now because I fixed the issue and closed this. But appreciate that I used the wrong version of rustup which sounds like it caused the issue.

[rbtcollins]

Ah, missed the age of rustup. Yes, lets close.