llvm21: drop libcxx and libunwind options (now part of llvm22)#61029
Draft
JkktBkkt wants to merge 1 commit into
Draft
llvm21: drop libcxx and libunwind options (now part of llvm22)#61029JkktBkkt wants to merge 1 commit into
JkktBkkt wants to merge 1 commit into
Conversation
Member
|
This doesn't need a rebuild. |
Member
|
I think it would make sense to just disable the build options instead of removing all the code. |
8168424 to
347c33d
Compare
Contributor
Author
|
Builds like this, after enabling libunwind and libcxx as runtimes, otherwise runs into void-packages/srcpkgs/llvm21/template Line 637 in 529624a Converted to draft: am going to run builds on other archs (including cross) and a test build. |
347c33d to
080c7a6
Compare
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
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.
Testing the changes
Local build testing
Closes #61005
I'm unsure if the revbump is necessary, there should be no functionality change from this, and this is addressing one of the roadblocks encountered in #59704
Based on bbdaa35 but I did not remove the lldb python integration.
[ci skip]