Merged
Conversation
1. Make the fips-boringssl-static profile point to BoringSSL commit 6d503ae1cf8b2e25162435225610b8c1f063d6f4, which is the latest revision that is available for download as a tarball from https://commondatastorage.googleapis.com/chromium-boringssl-fips 2. Update toolchain to clang-12 (required for compatibility with newer BoringSSL versions) 3. Remove CMAKE_POSITION_INDEPENDENT_CODE flag (flag seems redundant as BoringSSL manages PIC internally) 4. Fix bssl executable path (the bssl utility is now generated directly in the build directory rather than in a tool/ subdirectory) 5. Link with libdecrepit 6. Explicitly link with C++ standard library
Member
|
@jlnhws thanks! |
dongjoon-hyun
added a commit
to apache/spark
that referenced
this pull request
Mar 17, 2026
### What changes were proposed in this pull request? This PR aims to upgrade `netty-tcnative` to 2.0.75.Final. ### Why are the changes needed? To bring the latest bug fixes. - netty/netty-tcnative@netty-tcnative-parent-2.0.74.Final...netty-tcnative-parent-2.0.75.Final - netty/netty-tcnative#948 - netty/netty-tcnative#949 - netty/netty-tcnative#950 ### Does this PR introduce _any_ user-facing change? No behavior change. ### How was this patch tested? Pass the CIs. ### Was this patch authored or co-authored using generative AI tooling? No. Closes #54830 from dongjoon-hyun/SPARK-56009. Authored-by: Dongjoon Hyun <dongjoon@apache.org> Signed-off-by: Dongjoon Hyun <dongjoon@apache.org>
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
2 participants
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.
Make the
fips-boringssl-staticprofile point to BoringSSL commit6d503ae1cf8b2e25162435225610b8c1f063d6f4, which is the latest revision that is available for download as a tarball from https://commondatastorage.googleapis.com/chromium-boringssl-fipsUpdate toolchain to clang-12 (required for compatibility with newer BoringSSL versions)
Remove
CMAKE_POSITION_INDEPENDENT_CODEflag (seems redundant as BoringSSL manages PIC internally)Fix bssl executable path (the
bsslutility is now generated directly in the build directory rather than in atool/subdirectory)Link with libdecrepit
Explicitly link with C++ standard library