Skip to content

Commit 2ec519d

Browse files
committed
configure: a bare --enable-selftest means v2, not the v1 that cannot build
1 parent c0e4886 commit 2ec519d

1 file changed

Lines changed: 15 additions & 0 deletions

File tree

configure.ac

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8172,6 +8172,21 @@ AS_CASE([$ENABLED_SELFTEST],
81728172
SELFTEST_VERSION="v2"
81738173
],
81748174
["no"],[SELFTEST_VERSION="none"],
8175+
["yes"],[
8176+
# A bare --enable-selftest means the CURRENT selftest, which is v2.
8177+
# It used to fall through to the catch-all below and silently select
8178+
# v1 (wolfCrypt 3.14.2) -- a configuration that does not compile: v1
8179+
# withholds WC_SHA3_{224,256,384,512}_BLOCK_SIZE (sha3.h), which
8180+
# hash.h, hmac.h, hash.c, hmac.c and benchmark.c all reference
8181+
# unconditionally, and it declares a different wc_RsaPSS_CheckPadding_ex
8182+
# arity than asn.c calls. The Jenkins job is named
8183+
# PRB-CAVP-selftest-v2 and passes a bare --enable-selftest, so it was
8184+
# asking for v2 and being given a v1 that cannot build.
8185+
# --enable-selftest=v1 still selects v1 for anyone who explicitly wants
8186+
# it; only the bare form changed.
8187+
ENABLED_SELFTEST="yes"
8188+
SELFTEST_VERSION="v2"
8189+
],
81758190
[
81768191
# selftest v1 (wolfCrypt 3.14.2)
81778192
ENABLED_SELFTEST="yes"

0 commit comments

Comments
 (0)