Repository navigation
cmake: force secp256k1 ecmult settings past stale build caches - #30
Merged
Merged
Conversation
cryptoquick
changed the title
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Reconfiguring an existing build/ tree can leave SECP256K1_ECMULT_WINDOW_SIZE and SECP256K1_ECMULT_GEN_KB set to AUTO from older secp256k1 / older configures. secp256k1 v0.7.1 no longer accepts AUTO, so CMake fails before any code is built.
This PR pins both options to the upstream defaults (15 and 86) with CACHE … FORCE, next to the other secp256k1 options we already force. Fresh sandboxes (Nix, clean CI) are unaffected; this mainly fixes incremental host workflows without requiring rm -rf build.