-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
fix llvm_out
to use the correct LLVM root
#120721
fix llvm_out
to use the correct LLVM root
#120721
Conversation
(rustbot has picked a reviewer for you, use r? to override) |
llvm_out
to find the correct LLVM root.llvm_out
to find the correct LLVM root
d780721
to
d3848dc
Compare
This PR changes how LLVM is built. Consider updating src/bootstrap/download-ci-llvm-stamp. |
llvm_out
to find the correct LLVM rootprebuilt_llvm_config
to use the correct LLVM root
When `download-ci-llvm` is enabled, `llvm_out` ends up with the error below due to an incorrect path on cross-compilations. This change fixes that. ``` failed to execute command: "/rust/build/x86_64-unknown-linux-gnu/llvm/build/bin/llvm-config" "--version" ERROR: No such file or directory (os error 2) ``` Signed-off-by: onur-ozkan <work@onurozkan.dev>
d3848dc
to
7fb4512
Compare
prebuilt_llvm_config
to use the correct LLVM rootllvm_out
to use the correct LLVM root
Thanks for the PR! |
Signed-off-by: onur-ozkan <work@onurozkan.dev>
I just added a unit test for testing the behaviour of @bors r- |
Thanks for the PR! |
@bors r=albertlarsan68 rollup |
…cross-target, r=albertlarsan68 fix `llvm_out` to use the correct LLVM root When `download-ci-llvm` is enabled, `llvm_out` ends up with the error below due to an incorrect path on cross-compilations. This change fixes that. ```sh failed to execute command: "/rust/build/x86_64-unknown-linux-gnu/llvm/build/bin/llvm-config" "--version" ERROR: No such file or directory (os error 2) ```
Rollup of 13 pull requests Successful merges: - rust-lang#110482 (Add armv8r-none-eabihf target for the Cortex-R52.) - rust-lang#119162 (Add unstable `-Z direct-access-external-data` cmdline flag for `rustc`) - rust-lang#120302 (various const interning cleanups) - rust-lang#120455 ( Add FileCheck annotations to MIR-opt SROA tests) - rust-lang#120470 (Mark "unused binding" suggestion as maybe incorrect) - rust-lang#120479 (Suggest turning `if let` into irrefutable `let` if appropriate) - rust-lang#120564 (coverage: Split out counter increment sites from BCB node/edge counters) - rust-lang#120633 (pattern_analysis: gather up place-relevant info) - rust-lang#120664 (Add parallel rustc ui tests) - rust-lang#120721 (fix `llvm_out` to use the correct LLVM root) - rust-lang#120726 (Don't use bashism in checktools.sh) - rust-lang#120733 (MirPass: make name more const) - rust-lang#120735 (Remove some `unchecked_claim_error_was_emitted` calls) Failed merges: - rust-lang#120727 (exhaustiveness: Prefer "`0..MAX` not covered" to "`_` not covered") r? `@ghost` `@rustbot` modify labels: rollup
I got this linker-related rollout failure, could this be the culprit? |
I am not so sure. @bors rollup=iffy |
FWIW the rest of the rollup worked |
Two interesting things in the error output:
Googling around, it looks like Xcode 15 beta 3 has the same two things. Apparently because of the |
This doesn't look like a spurious failure at least. Maybe @rust-lang/bootstrap would know more? For the bootstrap team: this PR makes more use of the CI LLVM, which as far as I can tell triggered a problem with @bors r- From googling, suggested workaround is to use the |
I don't understand how this is relevant. Currently, |
Oh. removing this PR from the rollup fixed the error though, do you think it was a fluke? |
I think it was |
Alright then, I can't claim to understand much in this topic @bors r=albertlarsan68 rollup=iffy |
☀️ Test successful - checks-actions |
Finished benchmarking commit (68125c7): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Bootstrap: 666.849s -> 667.844s (0.15%) |
I stand corrected, sorry for making a fuss 🙏 |
When
download-ci-llvm
is enabled,llvm_out
ends up with theerror below due to an incorrect path on cross-compilations. This change fixes that.