Can't find LibCrypto on openSUSE Tumbleweed

[LorenDB]

I'm on openSUSE Tumbleweed with the latest SDK. Running CMake always gives me something along these lines:

# ...some general CMake output up here...

-- Encryption: LibCrypto
-- LibCrypto Include Dir: /usr/include
-- LibCrypto Shared Lib:  /usr/lib64/libcrypto.so
-- LibCrypto Static Lib:  crypto_STATIC_LIBRARY-NOTFOUND

# ...more output, then this...

CMake Error at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
  Could NOT find LibCrypto (missing: LibCrypto_LIBRARY)
Call Stack (most recent call first):
  /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:594 (_FPHSA_FAILURE_MESSAGE)
  crt/aws-crt-cpp/crt/s2n/cmake/modules/FindLibCrypto.cmake:71 (find_package_handle_standard_args)
  crt/aws-crt-cpp/crt/s2n/CMakeLists.txt:389 (find_package)


-- Configuring incomplete, errors occurred!
See also "/home/loren/code/aws-sdk-cpp/build/CMakeFiles/CMakeOutput.log".
See also "/home/loren/code/aws-sdk-cpp/build/CMakeFiles/CMakeError.log".

What could be the problem? I saw reports of needing a static OpenSSL build, but openSUSE doesn't provide one. Switching distros is currently not an option.

[jmklix]

What cmake command are you building with?

You might want to try setting USE_OPENSSL to OFF by adding this: -DUSE_OPENSSL=OFF

USE_OPENSSL

(Defaults to ON) Set this if you want to use your system's OpenSSL 1.0.2/1.1.1 compatible libcrypto

If disabled, SDK will build and install AWS-LC on Linux system when BUILD_DEPS is ON. This is an experimental feature. It will install AWS-LC as replacement of OpenSSL in the system default directory. Do not use if you have an OpenSSL installation in your system already.

[LorenDB]

I'm building with cmake -DBUILD_ONLY="core;s3" -DENABLE_TESTING=OFF ... Making that cmake -DUSE_OPENSSL=OFF -DBUILD_ONLY="core;s3" -DENABLE_TESTING=OFF .. doesn't help.

[SergeyRyabinin]

I would say that a fix similar to SDK's fix e5cda3f
should be applied on CRT libraries FindCrypto.cmake modules

[specious]

Commit e5cda3f partially addressed the issue but didn't fully fix it. See #1910.

[specious]

@LorenDB, I'm currently getting around this issue on Alpine Linux by doing this: #1910 (comment)

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.