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
Use case - build and tests using non-system default paths for executables and binaries.
Such environment allows functionality to use releases different from provided by OS.
[[ basis ]]
$ ./configure --help
CRYPTO_CFLAGS
C compiler flags for CRYPTO, overriding pkg-config
CRYPTO_LIBS linker flags for CRYPTO, overriding pkg-config
[[ part 1 ]]
Proposed correction is to update Makefile.am - prepend libraries and append flags:
Off-topic: for consistency curl flags should be listed as well.
[[ part 2 ]]
tpm2 tools depends from ssl library. Depending from linker (RPATH vs RUNPATH) above correction is not enough.
One solution is explicit list of ssl library.
To do correct static linking cryptographic libraries must be in right order -lssl -lcrypto.
Check for libssl will output only ssl library.
It seems to me check for libcrypto should be replaced by check for openssl.
Use case - build and tests using non-system default paths for executables and binaries.
Such environment allows functionality to use releases different from provided by OS.
[[ basis ]]
[[ part 1 ]]
Proposed correction is to update Makefile.am - prepend libraries and append flags:
Off-topic: for consistency curl flags should be listed as well.
[[ part 2 ]]
tpm2 tools depends from ssl library. Depending from linker (RPATH vs RUNPATH) above correction is not enough.
One solution is explicit list of ssl library.
This ensures working binary when linked produce binary with RUNPATH - ssl library located in location of cryptographic library.
Second solution is more complex - change configuration script pkg-config to check for libssl and to it.
The text was updated successfully, but these errors were encountered: