sasquatch: support gcc 10 #725
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
|
I forgot to increment the copyright to 2021, so I just quickly force-pushed real quick to fix that. |
|
done, thanks |
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.
Sasquatch apparently depends on
-fcommon, which was previously the default, but-fno-commonis now the default in GCC 10. @svenschwermer figured it out in devttys0/sasquatch#34, but @devttys0 hasn't merged it yet, so until that happens, this change simply makes the flag explicit in our ebuild.It's hard to tell because the diff adds a new file and isn't really a "diff" per se, but the new file is just a copy of
sasquatch-20180522.ebuildwith the lineEXTRA_CFLAGS=-fcommon \added, and the git commit bumped to the most recent version, for good measure.