summaryrefslogtreecommitdiff
path: root/tests/rustdoc-js-std/parser-errors.js
diff options
context:
space:
mode:
authorMatthias Krüger <matthias.krueger@famsik.de>2023-04-21 06:44:29 +0200
committerGitHub <noreply@github.com>2023-04-21 06:44:29 +0200
commitf2321ecce5d3ce9adedeb376f76492657478f5d1 (patch)
tree2edf18a61762757a87b0576d0e2ee78a1eef7a04 /tests/rustdoc-js-std/parser-errors.js
parent8d09b8e206c9993fca26309d6d0b5892ae845ca2 (diff)
parent68fc568b89b364025b6f4d1b364e26b4d5b1e79a (diff)
downloadrust-f2321ecce5d3ce9adedeb376f76492657478f5d1.tar.gz
Rollup merge of #110365 - ozkanonur:ship-tools-with-sysroot, r=jyn514
ship tools with sysroot Provides tool binaries under the sysroot which can be used/tested with `cargo +custom-toolchain $tool` Clippy and fmt works without any problem. But can't say the same for miri: ```sh  ~/devspace/.other/chunk-list  stable $ cargo +stage2 miri setup Running `"rustup" "component" "add" "rust-src"` to install the `rust-src` component for the selected toolchain. error: stage2 is a custom toolchain fatal error: failed to install the `rust-src` component for the selected toolchain ``` it's looking for `$sysroot/lib/rustlib/src/rust/library` and that simply doesn't exists for `x build`. cc `@jyn514` (I thought you might be interested on this, since you did few review iterations on previous PRs of adding tools to sysroot) -- **Update** Now we are able to use `miri` as well. After running `x b miri cargo-miri --stage 2`, I am able to run `cargo +stage2 miri setup` which works as expected. Resolves #110625 Resolves #97762 Resolves #81431
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions