mesa: add conflict with llvm@13#28870
Merged
haampie merged 2 commits intospack:developfrom Mar 1, 2022
Merged
Conversation
manuelakuhn
force-pushed
the
mesa-conflict-llvm13
branch
from
13d8e74 to
2ab5def
Compare
Member
Author
|
ping @chuckatkins @v-dobrev |
haampie
reviewed
Feb 22, 2022
Co-authored-by: Harmen Stoppels <[email protected]>
Member
Author
|
Is there anything left to do here? |
Member
|
Looks good to me, and I agree it should be a conflict on llvm itself, given that other libllvm providers should have their own explicit conflicts as major version numbers may or may not make sense for them (ping @kwryankrattiger) |
haampie
approved these changes
Mar 1, 2022
Member
Author
|
Thanks |
bvanessen
pushed a commit
to bvanessen/spack
that referenced
this pull request
Mar 2, 2022
Co-authored-by: Harmen Stoppels <[email protected]>
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
2 participants
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.
With the change to libllvm in #28365 the upper bound on llvm was removed although mesa does not build with llvm@13
see https://gitlab.freedesktop.org/mesa/mesa/-/issues/5455
@chuckatkins @v-dobrev