[do not merge] Test impact of secp256k1 endianness detection change #19695
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.
Do not merge this.
bitcoin-core/secp256k1#787 moves endianness detection from autotools to the C code, which seems doable on modern platforms, and simplifies getting things right on autotools-less environments.
As libsecp256k1 doesn't (yet) have MSVC-based ci, I'm (ab)using Bitcoin Core's for this change.