Moving from 1.11.283 to 1.11.420, build for s3 service only, got runtime error for missing shared library

[bzhou-sw]

Hi, we built our application with sdk 1.11.283 for s3 service only, and the application ran OK with 2 shared libs from sdk build, no other libs were needed.

libaws-cpp-sdk-core.so 
libaws-cpp-sdk-s3.so

But after moving to 1.11.420 with same build options and steps, the application now fails to start due to it is looking for libaws-crt-cpp.so now:

 error while loading shared libraries: libaws-crt-cpp.so: cannot open shared object file: No such file or directory

If I include libaws-crt-cpp.so in my container then it complained about other missing so:

error while loading shared libraries: libaws-c-common.so.1: cannot open shared object file: No such file or directory

and so on.

My build option (same for building 1.11.283 to 1.11.420):

rm -rf build
mkdir build
cd build
cmake .. \
    -DCMAKE_CXX_FLAGS="-D_FORTIFY_SOURCE=2 -fstack-protector -Werror=format-security -Wall -Wl,-z,relro,-z,now " \
    -DCMAKE_BUILD_TYPE=Release \
    -DBUILD_ONLY="s3" \
    -DENABLE_TESTING=OFF

make package

Why the new version looks for other libraries? Is there any new build options that I need?
Thanks a lot in advance

[jmklix]

We changed how this sdk depends on libcrypto back in May (1.11.283 is from March). We now depend on aws-crt-cpp for libcrypto (aws-crt-cpp -> aws-c-common -> aws-c-cal). This simplifies the dependencies for this sdk as it already depended on aws-crt-cpp. You can find the PR here with the changes.

As for why you're are getting a runtime error, you might need to git clone the submodules. You can update an existing clone with:

git submodule update --init --recursive

Detailed build steps can be found here. Please let me know if this doesn't fix it for you or if you have any other questions.

[bzhou-sw]

Thanks for your reply. We do have submodules, after build, we have following libs generated:

./build/crt/aws-crt-cpp/crt/aws-checksums/libaws-checksums.so
./build/crt/aws-crt-cpp/crt/aws-c-http/libaws-c-http.so
./build/crt/aws-crt-cpp/crt/aws-c-mqtt/libaws-c-mqtt.so
./build/crt/aws-crt-cpp/crt/aws-c-s3/libaws-c-s3.so
./build/crt/aws-crt-cpp/crt/aws-c-common/libaws-c-common.so
./build/crt/aws-crt-cpp/crt/aws-c-cal/libaws-c-cal.so
./build/crt/aws-crt-cpp/crt/aws-c-sdkutils/libaws-c-sdkutils.so
./build/crt/aws-crt-cpp/crt/aws-c-compression/libaws-c-compression.so
./build/crt/aws-crt-cpp/crt/aws-c-auth/libaws-c-auth.so
./build/crt/aws-crt-cpp/crt/aws-c-io/libaws-c-io.so
./build/crt/aws-crt-cpp/libaws-crt-cpp.so
./build/generated/src/aws-cpp-sdk-s3/libaws-cpp-sdk-s3.so
./build/src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so
./build/lib/libaws-c-event-stream.so
./build/lib/libs2n.so

We only need to access s3 and only want include necessary libs in our container. So are you saying we need and only need following to be able to access s3?

libaws-cpp-sdk-s3.so
libaws-cpp-sdk-core.so
libaws-crt-cpp.so
libaws-c-common.so
libaws-c-cal.so

[bzhou-sw]

It seems needs more libs. after adding crt, c-common, c-cal libs mentioned above, it complained about libaws-c-event-stream.so.1.0.0.
It worked after I included all built libs in my containers

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.