fix: release py-matplotlib from require: %clang #121
+0
−3
Conversation
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
Contributor
There was a problem hiding this comment.
Pull request overview
This PR removes the compiler-specific constraint requiring py-matplotlib to be built with Clang. The change allows py-matplotlib to use the default GCC compiler, assuming that previous issues with GCC and LTO have been resolved.
Key Changes
- Removed the
%clangrequirement for py-matplotlib from packages.yaml - py-matplotlib will now default to GCC compilation as per the global compiler preference
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
Briefly, what does this PR introduce?
This PR allows py-matplotlib to be compiled with gcc again as well. There are some issues with concretization when we have the clang constraint, so I'm hoping the issue with gcc and LTO is resolved by now...