Entry Point Not Found: AcquireSRWLockExclusive (KERNEL32.DLL) about curl-for-win

[vszakats]

The missing reference comes from OpenSSL 3.x, so the live build environment [Linux mingw-w64/clang cross-toolchain] isn't relevant here: https://github.com/openssl/openssl/blob/b3242ca622ef3da34ebb7b78b1f82cd5f0b516e7/crypto/threads_win.c#L76
It's referenced if _WIN32_WINNT >= 0x600 (= Vista or above).

curl-for-win does not override _WIN32_WINNT, and the toolchain / respective package defaults are used. Apparently these are not Windows XP compatible anymore.

One possible solution is to override the default with -D_WIN32_WINNT=0x0501 for x86 builds, another one is to build curl-for-win with Schannel support only. It may also be fixed/mitigated in OpenSSL.

[Fierelier]

I did curl https://curl.se, with success, on the following systems:

• Windows XP Professional Service Pack 3 (5.1.2600) - 32-bit
• Windows 7 Ultimate Service Pack 1 (6.1.7601) - 64-bit
  I can test on Windows 10 in a couple of hours, if no one else has done it till then.

[vszakats]

Thank you @Fierelier, I think this is fine for now. I'm more worried of future fallouts due to stepping off the default build path; so pushing this patch on an experimental note.

[jay]

Windows XP Professional Service Pack 3 (5.1.2600)

curl for windows official build is built using MSYS2 which requires the minimum OS to be Vista I think.

/cc @vszakats

[vszakats]

Can someone confirm if this test build works on various x86 Windows systems (XP included)?:
https://ci.appveyor.com/project/curlorg/curl-for-win/builds/43171473/artifacts

It includes this patch:
3188563

[Fierelier]

I did the same test on Windows 10 Home 21H2 (19044.1288) 64-bit with success. I'll do the same with W11 as well.

[Fierelier]

Actually, I'm burnt-out as-is with installing W10, I reckon it oughta run on W11.