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

// compile-flags: --target x86_64-unknown-uefi
// needs-llvm-components: x86
// rustc-env:CARGO=/usr/bin/cargo
#![feature(no_core)]
#![no_core]
extern crate core;
//~^ ERROR can't find crate for `core`
//~| NOTE can't find crate
//~| NOTE target may not be installed
//~| HELP consider building the standard library from source with `cargo build -Zbuild-std`
//~| HELP consider downloading the target with `rustup target add x86_64-unknown-uefi`
fn main() {}
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			`// compile-flags: --target x86_64-unknown-uefi`
Re-Annotate the tests with needs-llvm-components Doesn't work though, because compiletest doesn't process ignores on a per-revision manner. 2021-06-13 18:19:39 +00:00			`// needs-llvm-components: x86`
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			`// rustc-env:CARGO=/usr/bin/cargo`
Stop treating extern crate loading failures as fatal errors 2021-11-26 20:37:56 +00:00			`#![feature(no_core)]`
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			`#![no_core]`
			`extern crate core;`
			//~^ ERROR can't find crate for `core`
			`//~\| NOTE can't find crate`
			`//~\| NOTE target may not be installed`
			//~\| HELP consider building the standard library from source with `cargo build -Zbuild-std`
			//~\| HELP consider downloading the target with `rustup target add x86_64-unknown-uefi`
			`fn main() {}`