Statically link the legacy provider to endecode_test
authorMatt Caswell <matt@openssl.org>
Thu, 23 Dec 2021 13:59:12 +0000 (13:59 +0000)
committerMatt Caswell <matt@openssl.org>
Tue, 11 Jan 2022 11:00:21 +0000 (11:00 +0000)
commit7ee992a5d931ab5ad9df00d2d8e47e1b7a72d7ac
treefdb93056dfad82689d2361c9d79a4d493472682e
parentfbbe7202eba9fba243c18513f4f0316dafb3496d
Statically link the legacy provider to endecode_test

We already statically link libcrypto to endecode_test even in a "shared"
build. This can cause problems on some platforms with tests that load the
legacy provider which is dynamically linked to libcrypto. Two versions of
libcrypto are then linked to the same executable which can lead to crashes.

Fixes #17059

Reviewed-by: Paul Dale <pauli@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/17345)
crypto/build.info
test/build.info
test/endecode_test.c