This looks like a bug. Could you please submit the report via a GitHub
issue:
https://github.com/openssl/openssl/issues
Pauli
On 8/2/23 09:49, Thomas J. Hruska wrote:
On 2/7/2023 8:40 AM, OpenSSL wrote:
OpenSSL version 3.0.8 released
==============================
Hmm...the target VC-WIN64-ARM fails to build on VS2019. Previously
built fine for 3.0.7 but the newly released 3.0.8 does not
successfully build. The linker is complaining about _umul128, which
appears to be an Intel x64-specific intrinsic.
This commit appears to be responsible:
https://github.com/openssl/openssl/commit/b1892d21f8f0435deb0250f24a97915dc641c807
x86 and x64 builds work fine in their respective build environments.
...
Configuring OpenSSL version 3.0.8 for target VC-WIN64-ARM
...
"lib" /nologo /out:providers\libcommon.lib
@C:\Users\Redacted\AppData\Local\Temp\nmAA8B.tmp
IF EXIST .manifest DEL /F /Q .manifest
IF EXIST libcrypto-3-arm64.dll DEL /F /Q libcrypto-3-arm64.dll
cmd /C ""link" /nologo /debug /dll /NODEFAULTLIB:kernel32.lib
/APPCONTAINER /nologo /debug
@C:\Users\Redacted\AppData\Local\Temp\nmAACB.tmp /implib:libcrypto.lib
|| (DEL /Q libcrypto-3-arm64.* libcrypto.lib & EXIT 1)"
Creating library libcrypto.lib and object libcrypto.exp
libcrypto-shlib-rsa_sup_mul.obj : error LNK2019: unresolved external
symbol _umul128 referenced in function _mul_add_limb
libcrypto-3-arm64.dll : fatal error LNK1120: 1 unresolved externals
NMAKE : fatal error U1077: 'cmd' : return code '0x1'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual
Studio\2019\Community\VC\Tools\MSVC\14.29.30133\bin\HostX64\ARM64\nmake.exe"'
: return code '0x2'
Stop.
