Repository navigation
fix: re-point the cargo linker on a rust-llvm converge - #118
Merged
Merged
Conversation
hyperi-rust-setup names whatever clang resolves to as the cargo linker, but it was tagged rust-cache only, so --tags rust-llvm installed the new LLVM and left Rust linking with the previous clang.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
hyperi-rust-setup names whatever clang resolves to as the cargo linker, but it was tagged rust-cache only. So
--tags rust-llvminstalled LLVM 23 and left Rust linking with clang-21 through /usr/bin/clang.Adds rust-llvm to the rust-setup tasks. Validated on dragonfly: a rust-llvm converge now runs Configure the Rust build environment, failed=0, linker is /usr/local/bin/clang (23).
The doubled role run seen during validation is #92, commented there.