rust/tests/ui/crate-loading/missing-std.stderr

error[E0463]: can't find crate for `core`
  --> $DIR/missing-std.rs:6:1
   |
LL | extern crate core;
   | ^^^^^^^^^^^^^^^^^^ can't find crate
   |
   = note: the `x86_64-unknown-uefi` target may not be installed
   = help: consider downloading the target with `rustup target add x86_64-unknown-uefi`
   = help: consider building the standard library from source with `cargo build -Zbuild-std`

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0463`.
Give a better error when std or core are missing - Suggest using `rustup target add` if `RUSTUP_HOME` is set. I don't know if there's any precedent for doing this, but it seems harmless enough and it will be a big help. - Add a note about `#![no_std]` if `std` is missing but not core - On nightly, suggest using `cargo build -Z build-std` if `CARGO` is set - Add a note that std may be unsupported if `std` is missing but not core - Don't suggest `#![no_std]` when the load isn't injected by the compiler 2021-04-22 19:23:30 +00:00			error[E0463]: can't find crate for `core`
Stop treating extern crate loading failures as fatal errors 2021-11-26 20:37:56 +00:00			`--> $DIR/missing-std.rs:6:1`
Give a better error when std or core are missing - Suggest using `rustup target add` if `RUSTUP_HOME` is set. I don't know if there's any precedent for doing this, but it seems harmless enough and it will be a big help. - Add a note about `#![no_std]` if `std` is missing but not core - On nightly, suggest using `cargo build -Z build-std` if `CARGO` is set - Add a note that std may be unsupported if `std` is missing but not core - Don't suggest `#![no_std]` when the load isn't injected by the compiler 2021-04-22 19:23:30 +00:00			`\|`
			`LL \| extern crate core;`
			`\| ^^^^^^^^^^^^^^^^^^ can't find crate`
			`\|`
			= note: the `x86_64-unknown-uefi` target may not be installed
			= help: consider downloading the target with `rustup target add x86_64-unknown-uefi`
			= help: consider building the standard library from source with `cargo build -Zbuild-std`

Make not finding core a fatal error 2024-03-06 21:45:43 +00:00			`error: aborting due to 1 previous error`
Give a better error when std or core are missing - Suggest using `rustup target add` if `RUSTUP_HOME` is set. I don't know if there's any precedent for doing this, but it seems harmless enough and it will be a big help. - Add a note about `#![no_std]` if `std` is missing but not core - On nightly, suggest using `cargo build -Z build-std` if `CARGO` is set - Add a note that std may be unsupported if `std` is missing but not core - Don't suggest `#![no_std]` when the load isn't injected by the compiler 2021-04-22 19:23:30 +00:00
			For more information about this error, try `rustc --explain E0463`.