You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
aws-sdk-cpp build fails during building aws-c-io submodule
Regression Issue
Select this option if this issue appears to be a regression.
Expected Behavior
Build should be compeleted
Current Behavior
[ 20%] Building C object crt/aws-crt-cpp/crt/aws-c-io/CMakeFiles/aws-c-io.dir/source/posix/pipe.c.o
[ 21%] Building C object crt/aws-crt-cpp/crt/aws-c-io/CMakeFiles/aws-c-io.dir/source/posix/shared_library.c.o
[ 21%] Building C object crt/aws-crt-cpp/crt/aws-c-io/CMakeFiles/aws-c-io.dir/source/posix/socket.c.o
[ 21%] Building C object crt/aws-crt-cpp/crt/aws-c-io/CMakeFiles/aws-c-io.dir/source/retry_strategy.c.o
[ 21%] Building C object crt/aws-crt-cpp/crt/aws-c-io/CMakeFiles/aws-c-io.dir/source/s2n/s2n_tls_channel_handler.c.o
/home/user/Development/aws-sdk-cpp/crt/aws-crt-cpp/crt/aws-c-io/source/s2n/s2n_tls_channel_handler.c:27:14: fatal error: s2n/unstable/cleanup.h: No such file or directory
27 | # include <s2n/unstable/cleanup.h>
| ^~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
gmake[2]: *** [crt/aws-crt-cpp/crt/aws-c-io/CMakeFiles/aws-c-io.dir/build.make:342: crt/aws-crt-cpp/crt/aws-c-io/CMakeFiles/aws-c-io.dir/source/s2n/s2n_tls_channel_handler.c.o] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:619: crt/aws-crt-cpp/crt/aws-c-io/CMakeFiles/aws-c-io.dir/all] Error 2
gmake: *** [Makefile:136: all] Error 2
Describe the bug
aws-sdk-cpp build fails during building aws-c-io submodule
Regression Issue
Expected Behavior
Build should be compeleted
Current Behavior
Reproduction Steps
Possible Solution
This is happening after commit "dc41ddc498c10ebbf69aba7775afa36c8c1910bd" on Oct 10, 2024.
Temporarily workaround:
Additional Information/Context
Related issue on aws-sdk-cpp
aws-c-io version used
fcb38c8
Compiler and version used
gcc 11.4.0
Operating System and version
Ubuntu 22.04
The text was updated successfully, but these errors were encountered: