Update BoringSSL build #3737
Merged
Update BoringSSL build #3737
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
neuroradiology
approved these changes
Oct 27, 2025
Contributor
neuroradiology
left a comment
neuroradiology
left a comment
There was a problem hiding this comment.
Reviewed; agree with changes to boringssl libs.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #3735
This updates BoringSSL to their 20250818 release version, which is fairly recent. BoringSSL has a couple changes we need to accommodate: The branch name has changed to main and the build artifacts are up a level. This PR fixes those issues. Note that I'm not aware of any reason we cannot continue to move up to the current commit here, but my current build machine ships an old version of CMake BoringSSL just added a requirement prohibiting, so I'm stopping here for my convenience for now. I tested and libunwind-dev is indeed not required.
This commit will merge into the
devbranch, which is for community code changes post release 0.308.