Closed Lilit0x closed 6 months ago
I suspect the reason we're not seeing this failure in our CI is that we're not performing a --release
build. Optimized/release builds are more likely to produce such "maybe-uninitialized" variable warnings. In the cases above, I believe these are all actually false-positives from the compiler given how the variables are being used -- but that doesn't make this problem any less painful for our consumer.
I'd need to investigate what workarounds are available for this type of issue. I'm not sure that CFLAGS
gets propagated through. One option for now is to perform a debug build (instead of --release
). I hope to have a patch release available to address this issue soon.
I'm able to reproduce this error in our CI: https://github.com/aws/aws-lc-rs/actions/runs/8723216911/job/23930952090?pr=399
I'd need to investigate what workarounds are available for this type of issue. I'm not sure that
CFLAGS
gets propagated through. One option for now is to perform a debug build (instead of--release
). I hope to have a patch release available to address this issue soon.
I can confirm that debug builds compile successfully. I'll stick with that for now pending the fix. Thank you.
As of our v1.7.1 release, I believe this issue to be resolved. Feel free to reopen or create a new issue if you are still having a problem building aws-lc-rs. Thanks!
Problem:
I encountered a compilation issue when building my project that depends on
aws-lc-rs v1.7.0
for thex86_64-pc-windows-gnu
target. The compilation process fails with errors related to potentially uninitialized variables in theaws-lc
C code. I tried to suppress the warnings by setting theCFLAGS=-Wno-maybe-uninitialized
variable.I am using github actions CI for the build process:
Relevant details
AWS-LC for Rust versions: v1.7.0
System information: Github hosted windows runner
Build log: