dev-libs/libsecp256k1: fix build when CC is overridden to clang #35657
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.
The libsecp256k1 build system detects compiler flag feature support using
${CC}
but then builds the build-time executables using${CC_FOR_BUILD}
. WhenCC
andCC_FOR_BUILD
refer to different brands or versions of compilers, the feature detection for one will not be applicable to the other. Previous to this commit, our cross-compilation support patch attempted to override the flags when building the build-time executables, but it was doing so in a way that Automake does not respect. This commit fixes the patch so that Automake will actually useCFLAGS_FOR_BUILD
,CPPFLAGS_FOR_BUILD
, andLDFLAGS_FOR_BUILD
when building the build-time executables.Note: No revbump is needed since these ebuilds were failing to build on affected systems, and there are no changes in the installed files on unaffected systems.
Closes: https://bugs.gentoo.org/895048
@thesamesam