Could not create link from "cargo/bin/rustup" to "cargo/bin/rust-analyzer", Operation not permitted (os error 1)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 22h 40m
- Merged PRs (30d)
- 46
Description
Problem
I am trying to install rust on another usb device using rustup. I used CARGO_HOME and RUSTUP_HOME env variables to setup rustup path to be on the specific usb drive, when I install rustup it did not install and showed this error I used sudo before sh and it installed, but it didnt install any of the tool chains, so I found ansnwer to stack overflow that advised to type in the terminal "rustup install stable" So I did and it showed this error again, I tried again with sudo still showing this error
Steps
install rust with rustup on a differnet usb drive or maybe even path
add environment variables RUSTUP_HOME and CARGO_HOME to the path your installing to
run curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sudo sh
then when installed change the option of changing the path variable to no
once installed add rustup to path
then use rustup install stable to install rust
Possible Solution(s)
No response
Notes
No response
Rustup version
rustup 1.26.0 (5af9b9484 2023-04-05)
info: This is the version for the rustup toolchain manager, not the rustc compiler.
info: The currently active `rustc` version is `rustc 1.72.0 (5680fa18f 2023-08-23)`
Installed toolchains
Default host: x86_64-unknown-linux-gnu
rustup home: /media/elite_dev/Ventoy/softwares/rustup/
stable-x86_64-unknown-linux-gnu (default)
rustc 1.72.0 (5680fa18f 2023-08-23)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No project files or tests are named. Start by reproducing rustup install stable with RUSTUP_HOME and CARGO_HOME on the USB path, using the reported rustup 1.26.0 environment, and compare behavior with and without sudo. Done means identifying a reproducible cause and documenting or testing a fix for creating the rust-analyzer link.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100