rust-lang / rust-lang/rust-analyzer

build-std: ERROR Received compiler message for unknown package

Open
#21,602 7 comments 10 reactions 1 assignee View on GitHub

@pratham-srivastava-07 is already working on this.

Since Apr 11, 2026.

A-cargo C-bug
Dominant language
Rust
Stars
16.9k
Forks
2.2k
Avg merge
1d 12h
Merged PRs (30d)
72

Description

Short description

enabling build-std in .cargo/config.toml will result in ERRORs in the Output panel of VSCode pointing to compiler builtins.

Minimal reproduction:

https://github.com/tristanpoland/test_analyzer_bug
default hello world program, with .cargo/config.toml containing this:

[unstable]
build-std = ["core"]

It'll give these lines in the Output > rust-analyzer Language Server section:

[Error - 12:37:36 AM] Server process exited with code 0.
2026-02-08T00:37:36.907400434+01:00 ERROR Received compiler message for unknown package: path+file:///home/eurydice/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/compiler-builtins/compiler-builtins#compiler_builtins@0.1.160
 path+file:///home/eurydice/coreign/rustaxiomtest#0.1.0
2026-02-08T00:37:36.907447367+01:00 ERROR Received compiler message for unknown package: path+file:///home/eurydice/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/compiler-builtins/compiler-builtins#compiler_builtins@0.1.160
 path+file:///home/eurydice/coreign/rustaxiomtest#0.1.0

I don't know if these lines mean anything or if something failed at all, but I was having other problems in one of my local workspaces when I came across these lines in the output, and it looks like it's reproducible on nightly and stable, on both linux and windows.

rust-analyzer version: 1.95.0-nightly (f889772 2026-02-05) [/home/eurydice/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/bin/rust-analyzer]
rustc 1.95.0-nightly (f889772d6 2026-02-05)

extension version: rust-analyzer v0.3.2777

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.