libomp: Disable universal on Mojave+ #2661
Merged
Conversation
This file contains 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
macportsbot
added
by: member
|
Travis Build #3746 Passed. Lint resultsPort libomp success on xcode9.4. Log |
|
Travis is showing I haven't broken Pre-Mojave, so pulling the trigger. I don't have a Mojave system yet, see https://trac.macports.org/ticket/56720 for feedback from users. (Hopefully.) |
|
I think this was the right thing to do. (I've also tested it, and it works.) |
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.
Can't recall if this route (switching a portgroup on and off) is kosher, but that's what review is for, right?
Trying to address https://trac.macports.org/ticket/56720 sooner than waiting for a new port update since libomp is a dependency for many (via the clangs) ports.