-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FIPS fails to build with GCC >= 14 #569
Comments
Hello! Thanks for reporting this issue! I apologize for this build failure. This seems to be due to a gap in our CI coverage -- our CI tests with clang versions up to 18, but we've not yet added 19. (Note that there is also a known FIPS build issue with GCC v14.) As a workaround, older versions of Clang <= v18 (or GCC <= v13) should work for the FIPS build. We'll try to get this resolved for our next release. Thanks again! |
I looked a little more into this problem. This build failure was fixed last year on the AWS-LC main branch. This fix will likewise be included in our next FIPS (AWS-LC-FIPS 3.0) release, which is currently being tested. However, we don't yet have a date for that release. We'll be sure to inform our users as soon as our next FIPS release is available. |
Is it possible to do a check somewhere in CMake and stop the build when clang 19 or gcc 14 are detected? I think I hit this too, and it is very confusing! |
Hello! I updated the title as the latest version of |
Problem:
cargo check
fails when using clang 19 for FIPS builds. AFAICT it's because AWS-LC is pinned to a specific commit (ec94d74), which has a cast operation in it that newer versions of clang rejects. I did try upgrading to AWS-LC-FIPS-2.0.17, but it appears the issue is still there andcargo check
still fails.Relevant details
AWS-LC for Rust versions or commit: (6b1bce0...)
System information: for linux, below info can be collected by running
uname -srvmp
Build log:
The text was updated successfully, but these errors were encountered: