https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=try 2023-01-11T09:32:08+00:00 2023-01-11T09:32:08+00:00 Albert Larsan 74931857+albertlarsan68@users.noreply.github.com 2023-01-05T08:13:28+00:00 urn:sha1:cf2dff2b1e3fa55fa5415d524200070d0d7aacfe 2021-12-01T21:04:13+00:00 Michael michael.prantl@hotmail.de 2021-11-26T20:37:56+00:00 urn:sha1:62f4ce993e8aa788c8269d75aea2db84cafb1f9f 2021-07-24T01:29:42+00:00 Joshua Nelson jyn514@gmail.com 2021-07-22T02:04:05+00:00 urn:sha1:17f7536fb220fc53cd0af2de46528070cfab012c 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-06-24T20:13:08+00:00 Simonas Kazlauskas git@kazlauskas.me 2021-06-13T18:19:39+00:00 urn:sha1:493fe8008b33c576240bfa6979760e0e5482d5af Doesn't work though, because compiletest doesn't process ignores on a per-revision manner. 2021-04-25T16:45:31+00:00 Joshua Nelson jyn514@gmail.com 2021-04-22T19:23:30+00:00 urn:sha1:d326a4b4c9176193ff0ac445ec14ac50bd081f04 - 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