-
Notifications
You must be signed in to change notification settings - Fork 614
workaround(coin-or-Cbc): Disable HiGHS support #16626
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,25 @@ | ||
| [components.coin-or-Cbc] | ||
|
|
||
| # coin-or-HiGHS is not available in Azure Linux. Disable HiGHS support by | ||
| # removing the HiGHS BuildRequires entry and stripping the configure flags. | ||
| # HiGHS is an optional LP solver backend; Cbc's primary solver (Clp) is unaffected. | ||
|
|
||
| [[components.coin-or-Cbc.overlays]] | ||
| description = "Disable HiGHS BuildRequires — coin-or-HiGHS not available in Azure Linux" | ||
| type = "spec-remove-tag" | ||
| tag = "BuildRequires" | ||
| value = "pkgconfig(highs)" | ||
|
|
||
| [[components.coin-or-Cbc.overlays]] | ||
| description = "Remove HiGHS --with-highs-incdir configure flag" | ||
| type = "spec-search-replace" | ||
| section = "%build" | ||
| regex = ' --with-highs-incdir=%\{_includedir\}/highs \\' | ||
| replacement = " \\" | ||
|
|
||
| [[components.coin-or-Cbc.overlays]] | ||
| description = "Remove HiGHS --with-highs-lib configure flag" | ||
| type = "spec-search-replace" | ||
| section = "%build" | ||
| regex = ' --with-highs-lib=-lhighs \\' | ||
| replacement = " \\" | ||
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The two
spec-search-replaceoverlays replace the HiGHS configure-option lines with a standalone line-continuation (\). That leaves “empty” continuation lines in the%configureinvocation, which is harder to reason about and can be brittle if the surrounding%configureformatting changes.Since the upstream spec already isolates all HiGHS logic under
%ifnarch %{ix86}(only two occurrences, both for HiGHS), consider making the workaround more robust by disabling that conditional block entirely (e.g., replace%ifnarch %{ix86}with an always-false%if 0) or by replacing the whole option line with an empty string (so the option line disappears rather than becoming a bare continuation).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Already considered. See my comment here #16626 (comment)