os-rust/tests/ui/issues/issue-37131.stderr

error[E0463]: can't find crate for `std`
   |
   = note: the `thumbv6m-none-eabi` target may not be installed
   = help: consider downloading the target with `rustup target add thumbv6m-none-eabi`
   = 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`.
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00			error[E0463]: can't find crate for `std`
			`\|`
			= note: the `thumbv6m-none-eabi` target may not be installed
Remove detection of rustup and cargo in 'missing extern crate' diagnostics Previously, this would change the test output when RUSTUP_HOME was set: ``` ---- [ui] ui/issues/issue-49851/compiler-builtins-error.rs stdout ---- diff of stderr: 1 error[E0463]: can't find crate for `core` 2 \| 3 = note: the `thumbv7em-none-eabihf` target may not be installed + = help: consider downloading the target with `rustup target add thumbv7em-none-eabihf` 4 5 error: aborting due to previous error 6 ``` Originally, I fixed it by explicitly unsetting RUSTUP_HOME in compiletest. Then I realized that almost no one has RUSTUP_HOME set, since rustup doesn't set it itself; although it does set RUST_RECURSION_COUNT whenever it launches a proxy. Then it was pointed out that this runtime check doesn't really make sense and it's fine to make it unconditional. 2021-07-22 02:04:05 +00:00			= help: consider downloading the target with `rustup target add thumbv6m-none-eabi`
			= help: consider building the standard library from source with `cargo build -Zbuild-std`
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00
Make not finding core a fatal error 2024-03-06 16:45:43 -05:00			`error: aborting due to 1 previous error`
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00
			For more information about this error, try `rustc --explain E0463`.