-
Notifications
You must be signed in to change notification settings - Fork 13.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
boostrap: skip no_std targets in Std doc step #137073
boostrap: skip no_std targets in Std doc step #137073
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @clubby789 (or someone else) some time within the next two weeks. Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (
|
Seems reasonable, thanks! @bors r+ |
…iaskrgr Rollup of 9 pull requests Successful merges: - rust-lang#136959 (Simplify switch sources) - rust-lang#137020 (Pass vendored sources from bootstrap to generate-copyright) - rust-lang#137073 (boostrap: skip no_std targets in Std doc step) - rust-lang#137165 (Use `tell` for `<File as Seek>::stream_position`) - rust-lang#137166 (Update default loongarch code model in docs) - rust-lang#137168 (correct comment) - rust-lang#137169 (CI: rfl: move job forward to Linux v6.14-rc3) - rust-lang#137170 (Allow configuring jemalloc per target) - rust-lang#137173 (Subtree update of `rust-analyzer`) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of rust-lang#137073 - niklaskorz:bootstrap-doc-fix-empty-no-std, r=clubby789 boostrap: skip no_std targets in Std doc step This fixes a bug that currently prevents us from adding no_std library targets to rustc in nixpkgs (NixOS/nixpkgs#382166). When running `./x.py doc`, the `Std` doc step generally fails for no_std targets, logs: https://gist.github.com/niklaskorz/fb83f9503ce19b75e8b1af02cdebd592 Skipping no_std targets in this step will allow using no_std targets such as `bpfel-unknown-none` together with other targets in the same config without blocking the doc generator for them, e.g. ``` ./configure --release-channel=stable --tools=rustc,rustdoc,rust-analyzer-proc-macro-srv --build=aarch64-apple-darwin --host=aarch64-apple-darwin --target=aarch64-apple-darwin,bpfel-unknown-none ./x.py doc ``` Logs with this fix applied: https://gist.github.com/niklaskorz/cdd50aaea33ede579f737434286d800b
This fixes a bug that currently prevents us from adding no_std library targets to rustc in nixpkgs (NixOS/nixpkgs#382166).
When running
./x.py doc
, theStd
doc step generally fails for no_std targets, logs: https://gist.github.com/niklaskorz/fb83f9503ce19b75e8b1af02cdebd592Skipping no_std targets in this step will allow using no_std targets such as
bpfel-unknown-none
together with other targets in the same config without blocking the doc generator for them, e.g.Logs with this fix applied: https://gist.github.com/niklaskorz/cdd50aaea33ede579f737434286d800b