Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

GCC-14 - build failure for FIPS module #2010

Open
justsmth opened this issue Nov 25, 2024 · 0 comments
Open

GCC-14 - build failure for FIPS module #2010

justsmth opened this issue Nov 25, 2024 · 0 comments

Comments

@justsmth
Copy link
Contributor

Problem:

FIPS module fails to build when using GCC 14.

Related Issues

Relevant details

AWS-LC commit: AWS-LC-FIPS-2.0.17, but this affects the mainline builds as well.

System information: for linux, below info can be collected by running uname -srvmp

  • CPU architecture: x86-64
  • OS: Ubuntu 24.04

Build log:

2024/11/23 00:55:59 WARN   error while processing "\t.section\t.data.rel.ro.local,\"aw\"\n" on line 444986: ".data section found in module"
samuel40791765 added a commit that referenced this issue Dec 12, 2024
Alpine Linux has started using gcc-14 as the default compiler. This is
broken with our FIPS build which has started causing CI failures. See
#2010

By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 license and the ISC license.
torben-hansen pushed a commit to torben-hansen/aws-lc that referenced this issue Dec 13, 2024
Alpine Linux has started using gcc-14 as the default compiler. This is
broken with our FIPS build which has started causing CI failures. See
aws#2010

By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 license and the ISC license.
michelhe added a commit to michelhe/aws-lc-rs that referenced this issue Jan 28, 2025
The underlying aws-lc library is broken when built with FIPS support on GCC-14,
which comes by default with many Linux distributions.

When this crate is used as a sub-dependency, the users' only workaround is to force
all C/C++ code on other crates to also be compiled with clang by setting the CC/CXX environment variables.

This change circumvents the issue by setting the CC/CXX environment variables in the crate
build script.

This is a temporary workaround until the underlying issue is resolved:
aws/aws-lc#2010

Signed-off-by: Michel Heily <michel.heily@wiz.io>
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant