Replies: 2 comments 1 reply
-
Update: |
Beta Was this translation helpful? Give feedback.
1 reply
-
I wasn't able to solve the issue. I had to resort to using the embedded C SDK instead in my application. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
When running an application using other shared libraries with the sdk configured with
-DUSE_OPENSSL=ON
I get an error durings2n_init()
I've tried all the options discussed in the 414 discussion with no success.
The SDK is configured with the following CMake options:
CMake and the build finish successfully.
I'm able to build and run a sample app that only uses the SDK but as soon as I add a 3rd party library, I get the above error.
I added a print message to check the version of OpenSSL loaded. The same version that's printed out during the SDK configure and build process is printed out at run-time.
I checked the other 3rd party library and it doesn't appear to be using OpenSSL or libcrypto but does use libssh2-1 which depends on libcrypt20.
If I build without
-DUSE_OPENSSL=ON
I get the following when building my app:Platform
OS: Linux Mint
CPU: x86_64
Openssl Version 3.0.2
GCC 11.3.0
Any help would be appreciated!
Beta Was this translation helpful? Give feedback.
All reactions