Skip to content

Conversation

@jlnhws
Copy link
Contributor

@jlnhws jlnhws commented Nov 24, 2025

  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 (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

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
@normanmaurer normanmaurer added this to the 2.0.75.Final milestone Dec 8, 2025
@normanmaurer normanmaurer merged commit b94455e into netty:main Dec 8, 2025
10 checks passed
@normanmaurer
Copy link
Member

@jlnhws thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants