diff options
author | Sebastian Andrzej Siewior <sebastian@breakpoint.cc> | 2018-01-25 22:50:55 +0100 |
---|---|---|
committer | Richard Levitte <levitte@openssl.org> | 2018-03-15 11:59:08 +0100 |
commit | 9e381e8a018592a2a42e83df402e1ef921469e9f (patch) | |
tree | a9c4cf2f2505680176b92573e7fbc6b82e380691 /Configure | |
parent | 16ff13427f00753a76672317143753b83cea7982 (diff) |
Configure: allow to enable afalgeng if target does not start with Linux
The Debian build system uses a `debian' target which sets CFLAGS and
then we have for instance debian-amd64 which inherits from
linux-x86_64 and debian [0]. So far so good.
Unless there are different suggestions how to do this, I would keep it.
However since the target name does not start with `linux', the build
system does not enable the afalg engine. So in order to get enabled, I
added a
`enable => [ "afalgeng" ],'
to the generic linux config which sets it explicit (as suggested by
Richard Levitte). Having this set, we can check for it instead matching
the target name.
[0] https://sources.debian.org/src/openssl/1.1.0g-2/Configurations/20-debian.conf/
Signed-off-by: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
Reviewed-by: Matt Caswell <matt@openssl.org>
Reviewed-by: Richard Levitte <levitte@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/5169)
Diffstat (limited to 'Configure')
-rwxr-xr-x | Configure | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -1518,7 +1518,7 @@ unless ($disabled{"crypto-mdebug-backtrace"}) unless ($disabled{afalgeng}) { $config{afalgeng}=""; - if ($target =~ m/^linux/) { + if (grep { $_ eq 'afalgeng' } @{$target{enable}}) { my $minver = 4*10000 + 1*100 + 0; if ($config{CROSS_COMPILE} eq "") { my $verstr = `uname -r`; |