Add boost 1.92.0 0 #386
Merged
Add boost 1.92.0 0 #386
Conversation
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
Update to the latest upstream release, 1.92.0 from 2026-08-05. Bind Boost.Python against python-3.14.6-2, the newest installed Python package, instead of the no longer current python-3.11.7-1. Assisted-by: Claude Opus 5 <noreply@anthropic.com>
The script trusted whatever the mirror returned. A truncated download or a swapped object on beehive would have been fed straight into tar, and because the tarball is kept in $BUILDDIR a partial file also survived into every later run. No new constant is needed: the md5 sum is already the path component of the beehive URL, so read it back out with basename/dirname. The URL stays a single literal that can be pasted from the md5repo.sh output unchanged, and the sum can never fall out of step with the object it names. Run on every invocation, not just after a fresh download, so a bad cached tarball is caught too. With set -e a mismatch aborts before tar. Checked both directions against the local copy: boost_1_92_0.tar.gz: OK boost_1_92_0.tar.gz: FAILED md5sum: WARNING: 1 computed checksum did NOT match GNU coreutils recommends cksum -a md5 over md5sum these days, but /bin here is coreutils 8.31, whose cksum predates -a and does CRC only: cksum: invalid option -- 'a' Assisted-by: Claude Opus 5 <noreply@anthropic.com>
The rpath fixup iterated over *$VERSION. An unmatched glob expands to the pattern itself, test -e is not consulted, and patchelf was handed a name that does not exist. Under set -x that one error scrolled past in a very long log, and the loop’s exit status was that of the last iteration, so a naming change upstream would have shipped libraries without an rpath and the build would still have reported success. Anchor the glob at libboost_*.so.$VERSION, break out when the pattern fails to match, and abort if nothing was patched at all. Replayed against the installed /pkg/boost-1.86.0-0/lib with patchelf stubbed out; new and old glob select the same set: matched 43 libraries 43 and the unmatched case now stops the build instead of limping on: no libboost_*.so.9.99.9, rpath left unset rc=1 Assisted-by: Claude Opus 5 <noreply@anthropic.com>
Sign in
to join this conversation on GitHub.
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.
No description provided.