no-module should not imply disabling DSO loading support
Reviewed-by: Matt Caswell <matt@openssl.org>
Reviewed-by: Dmitry Belyavskiy <beldmit@gmail.com>
Reviewed-by: Paul Dale <pauli@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/21459)
(cherry picked from commit 3d2f96e2c8
)
This commit is contained in:
parent
4ab5a874cc
commit
e1ec729a17
|
@ -597,8 +597,7 @@ my @disable_cascades = (
|
|||
|
||||
"crypto-mdebug" => [ "crypto-mdebug-backtrace" ],
|
||||
|
||||
# If no modules, then no dynamic engines either
|
||||
"module" => [ "dynamic-engine" ],
|
||||
"module" => [ "dynamic-engine", "fips" ],
|
||||
|
||||
# Without shared libraries, dynamic engines aren't possible.
|
||||
# This is due to them having to link with libcrypto and register features
|
||||
|
@ -616,8 +615,6 @@ my @disable_cascades = (
|
|||
# or modules.
|
||||
"pic" => [ "shared", "module" ],
|
||||
|
||||
"module" => [ "fips", "dso" ],
|
||||
|
||||
"engine" => [ "dynamic-engine", grep(/eng$/, @disablables) ],
|
||||
"dynamic-engine" => [ "loadereng" ],
|
||||
"hw" => [ "padlockeng" ],
|
||||
|
|
Loading…
Reference in New Issue