Repository navigation
Conversation
b2 install does not implement DESTDIR the way autotools/CMake do: every libboost_*.dylib ships with a bare (or, for libboost_filesystem, an @rpath) install name and bare/@rpath intra-bundle dependency references, with no LC_RPATH anywhere to resolve them -- confirmed by parsing the published tarball's Mach-O load commands directly. yaml-cpp has the same @rpath defect; GSL/gslcblas/FFTW3 already got their own install names right. None of this is loadable without DYLD_LIBRARY_PATH, which SIP strips on GitHub's runners whenever a protected binary (/bin/sh, /usr/bin/python3, ...) is exec'd -- not a usable workaround. fix-install-names.bash normalises every dylib's install name and every intra-bundle dependency reference to its final absolute ${PREFIX}/lib/<name> path (applied uniformly to all four dependencies, not just Boost, since the same loop covers them), re-signing ad-hoc after each install_name_tool rewrite invalidates the signature. verify-bundle.bash then re-checks the assembled tarball end-to-end before it is pushed -- absolute install names, no bare/@rpath/DESTDIR references, no LC_RPATH, valid signatures -- so a future dependency bump can't reintroduce this silently. Both scripts were exercised against a harness standing in for otool/install_name_tool/codesign (seeded from the real tarball's load commands), not against the real tools on real macOS hardware.
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.
b2 install does not implement DESTDIR the way autotools/CMake do: every libboost_*.dylib ships with a bare (or, for libboost_filesystem, an @rpath) install name and bare/@rpath intra-bundle dependency references, with no LC_RPATH anywhere to resolve them -- confirmed by parsing the published tarball's Mach-O load commands directly. yaml-cpp has the same @rpath defect; GSL/gslcblas/FFTW3 already got their own install names right. None of this is loadable without DYLD_LIBRARY_PATH, which SIP strips on GitHub's runners whenever a protected binary (/bin/sh, /usr/bin/python3, ...) is exec'd -- not a usable workaround.
fix-install-names.bash normalises every dylib's install name and every intra-bundle dependency reference to its final absolute ${PREFIX}/lib/ path (applied uniformly to all four dependencies, not just Boost, since the same loop covers them), re-signing ad-hoc after each install_name_tool rewrite invalidates the signature. verify-bundle.bash then re-checks the assembled tarball end-to-end before it is pushed -- absolute install names, no bare/@rpath/DESTDIR references, no LC_RPATH, valid signatures -- so a future dependency bump can't reintroduce this silently.