-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rust anaylzer fails to compile crates which build properly with cargo build
#17615
Comments
Does |
@lnicola Yes happy to provide additional information or try different steps thanks again |
Any |
I appreciate you taking the time to help
as in like randomly in my file system? there shouldnt be
I genuinely have no clue I thought they were something specific to the crate I installed the rust toolchain today via fenix Is there anything else I can do to help you? |
Sorry,
No, I think it will fail even without dependencies.
I don't know anything about Nix, sorry 😔. Normally, |
both I really dont see how this would be a nix thing just to try it I removed the fenix stuff, just installed rustup as a nix package (no different than downloading it) then running
so I should have a regular rustup install so that path exists on my machine:
same issue remains |
Can you try building with rust-analyzer via task? That should pop up a new terminal tab showing what command is being run, including what cargo specifically. Ctrl/⌘+Shift+P -> |
main.rs -> Ctrl/⌘+Shift+P -> rust-analyzer: Run ->
(there was also same error as at the start still present in rust-analyzer output |
Hi, I've run into an issue I believe to share a root cause. In my example repo I make use of cargo.toml and am able to reproduce the behavior of rust-analyzer rejecting code that rustc is happy to compile. OS: Win 11 Home 22H2 (22621.3880) This behavior seems to have manifested itself somewhat recently for me. Maybe around 2 - 3 weeks ago. It's been a while since I had worked in the affected repository and longer since a toolchain upgrade so I cannot be sure. This repo replicates the issue using It does seem to be an issue in part with the |
I've tracked my issue to nightly-2024-06-24-x86_64-pc-windows-msvc. Ill see if I can try to find the specific commit tonight or tomorrow. |
really appreciate you taking a look |
I will move to a new issue then. |
sure |
I think your issue is resolved by #17697 |
Regarding the original issue, I am a bit stumped here as well |
rust-analyzer version: (eg. output of "rust-analyzer: Show RA Version" command, accessible in VSCode via Ctrl/⌘+Shift+P)
0.3.2037-standalone (e9afba5 2024-07-14)
rustc version: (eg. output of
rustc -V
)rustc 1.79.0 (129f3b996 2024-06-10)
editor or extension: (eg. VSCode, Vim, Emacs, etc. For VSCode users, specify your extension version; for users of other editors, provide the distribution if applicable)
vscode
relevant settings: (eg. client settings, or environment variables like
CARGO
,RUSTC
,RUSTUP_HOME
orCARGO_HOME
)none
===
I am on macos
I have a barebones
cargo init
project just with theuncased
crate added in cargo.toml (the issue is not specific to this crate, it happens with others too)cargo build
runs just finebut rust analyzer is unable compile it
Im a bit confused how
rust-lld.exe
would ever be called on macosany help is appreciated thanks
The text was updated successfully, but these errors were encountered: