Rust errors / Names, paths and imports
Rust compiler error · checked with rustc 1.99.0
Rust error E0463: can't find crate for `foo`
What it meansA crate was declared but cannot be found.
What rustc prints
error[E0463]: can't find crate for `foo`
--> main.rs:1:1
|
1 | extern crate foo; // error: can't find crate
| ^^^^^^^^^^^^^^^^^ can't find crateReal output of rustc 1.99.0 compiling the official example below (2021 edition). Your names and line numbers will differ; the first line is the part to match.
E0463Names, paths and imports
Activein rustc 1.99.0
8related errors linked below
The compiler team's explanation
A crate was declared but cannot be found.
Erroneous code example:
extern crate foo; // error: can't find crateYou need to link your code to the relevant crate in order to be able to use it (through Cargo or the -L option of rustc, for example).
Common causes
- The crate is not present at all. If using Cargo, add it to
[dependencies]in Cargo.toml. - The crate is present, but under a different name. If using Cargo, look for
package =under[dependencies]in Cargo.toml.
Common causes for missing std or core
- You are cross-compiling for a target which doesn't have
stdprepackaged. Consider one of the following: + Adding a pre-compiled version of std withrustup target add+ Building std from source withcargo build -Z build-std+ Using#![no_std]at the crate root, so you won't needstdin the first place. - You are developing the compiler itself and haven't built libstd from source. You can usually build it with
x.py build library/std. More information about x.py is available in the rustc-dev-guide.
From rustc --explain E0463 (1.99.0), part of the Rust project, MIT or Apache-2.0. Official page.
Related errors
- E0425cannot find value in this scope
- E0603is private
- E0432unresolved import
- E0005refutable pattern in local binding
- E0460Found possibly newer version of crate `..` which `..` depends on
- E0461Couldn't find crate `..` with expected target triple `..`
- E0464The compiler found multiple library files with the requested crate name
- E0468an `extern crate` loading macros must be at the crate root
Up next
Often hit nextE0425: cannot find value in this scopeA related error from the same family.Read it next →Did this answer your question?