guix: increase maximum allowed (runtime) GCC to 7
What the developer wrote
Authored by fanquake
guix: increase maximum allowed (runtime) GCC to 7
Fixes:
```bash
/distsrc-base/distsrc-d3b8a54a8120-x86_64-linux-gnu/build/bin/bitcoind: symbol __divmodti4 from unsupported version GCC_7.0.0(14)
/distsrc-base/distsrc-d3b8a54a8120-x86_64-linux-gnu/build/bin/bitcoind: failed IMPORTED_SYMBOLS
```
which is occuring after #32750. I can't see any supported distro that is
shipping a new enough glibc (2.31), but a GCC older than 7.0.
What changed, and why it matters
This commit loosens an internal build-time check that verifies which compiler/library versions Bitcoin Core's release binaries are allowed to depend on. It does not change the actual code users run, fix a crash in normal operation, or patch a vulnerability. The change was needed because a recent code update (#32750) legitimately uses a compiler helper symbol that only exists in GCC 7+, so the release-build script had to be updated to permit that symbol. No security bug is being fixed.
No security action required. Treat as a normal build-system maintenance commit. Reviewers may want to confirm that the raised GCC bound still matches the project's documented minimum toolchain policy, but the change itself is benign.
Security signals we found
No memory-safety, cryptographic, or consensus code changed
No input validation, parsing, or network logic changed
Change is confined to a release-build symbol-version linter
The referenced symbol (__divmodti4 GCC_7.0.0) is a compiler runtime helper, not a vulnerability
Commit message frames the change as a build fix, not a security fix
Evidence from the diff
The patch updates contrib/guix/symbol-check.py, a Guix release-build lint script, raising the maximum permitted GCC symbol version from 4.3.0 to 7.0.0. After PR #32750 the compiled bitcoind binary imports __divmodti4 from GCC_7.0.0, causing the symbol-checker to reject the build. The author notes no supported distro ships glibc 2.31 (the existing maximum) alongside GCC older than 7.0, so the raised GCC bound is consistent with the existing GLIBC bound and does not meaningfully widen real-world compatibility. This is a build-script tolerance adjustment, not a runtime behavior change.
Changed components
contrib/guix/symbol-check.pyInspect captured patch +1 / −1
diff --git a/contrib/guix/symbol-check.py b/contrib/guix/symbol-check.py
index 91241eda..b5093f34 100755
--- a/contrib/guix/symbol-check.py
+++ b/contrib/guix/symbol-check.py
@@ -32,7 +32,7 @@ import lief
# See https://gcc.gnu.org/onlinedocs/libstdc++/manual/abi.html for more info.
MAX_VERSIONS = {
-'GCC': (4,3,0),
+'GCC': (7,0,0),
'GLIBC': {
lief.ELF.ARCH.X86_64: (2,31),
lief.ELF.ARCH.ARM: (2,31),
Why this scored 17/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.