OpenSSL linkage error on test-rackspace-win2022_vs2022-x64-3

[Renegade334]

It's unclear when exactly this started occurring, but at least since 28th February, win-vs2022_clang-arm64 has been failing on test-rackspace-win2022_vs2022-x64-3 specifically, with the following linker error:

lld-link : error : undefined symbol: ossl_gost18_cke_cipher_nid [C:\workspace\node-compile-windows\node\deps\openssl\openssl-cli.vcxproj]
  >>> referenced by C:\workspace\node-compile-windows\node\deps\openssl\openssl\ssl\statem\statem_srvr.c:3354
  >>>               openssl.lib(statem_srvr.obj):(tls_process_cke_gost18)
lld-link : error : undefined symbol: ossl_gost_ukm [C:\workspace\node-compile-windows\node\deps\openssl\openssl-cli.vcxproj]
  >>> referenced by C:\workspace\node-compile-windows\node\deps\openssl\openssl\ssl\statem\statem_srvr.c:3362
  >>>               openssl.lib(statem_srvr.obj):(tls_process_cke_gost18)

Don't know if that's genuinely the first appearance. The error ends up getting logged to the reliability repo as sh: line 12: [: -gt: unary operator expected due to a missing output in a later shell script.

[richardlau]

CC @StefanStojanovic

[StefanStojanovic]

Good catch. This only happens on one machine and only for ARM64 cross-compilation. Most likely, some configuration issue caused by some update, or something like that. For now, I've disabled ARM64 compilation on this machine, so no PRs should be blocked on it.