WolfSSL
/
wolfssh
mirror of https://github.com/wolfSSL/wolfssh.git
1
0
Fork 0
Code Issues Releases Wiki Activity

windows-check: Link ws2_32 and crypt32 for the mingw-regress wolfssh build 

config.log from a failing run showed the wolfCrypt_Init AC_CHECK_LIB
probe pulling in ssl.c/internal.c/wolfio.c from the static
libwolfssl.a, leaving Winsock (socket, send, recv, inet_pton, ...) and
cert store (CertOpenSystemStoreA, ...) symbols unresolved. A shared
build would defer that resolution to the DLL; the static archive here
needs ws2_32 and crypt32 passed explicitly via LIBS.
pull/1247/head
Hideki Miyazaki 2026-09-04 13:05:51 -04:00 committed by John Safranek
parent 3532cc4432
commit 90ce9fb61b
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
.github/workflows/windows-check.yml vendored
View File

@ -288,9 +288,13 @@ jobs:
# autogen.sh exports WARNINGS="all,error", turning autotools warnings
# into errors that the MSYS2 automake can trip on.
autoreconf -ivf
# wolfssl is a static archive here, so its Windows socket (ws2_32) and
# certificate store (crypt32) references are only resolved when this
# configure's own AC_CHECK_LIB and later link steps pull them in too.
./configure --enable-sftp \
CPPFLAGS="-I$HOME/wolfssl-install/include" \
LDFLAGS="-L$HOME/wolfssl-install/lib"
LDFLAGS="-L$HOME/wolfssl-install/lib" \
LIBS="-lws2_32 -lcrypt32"
make -j$(nproc) tests/regress.test tests/unit.test
./tests/regress.test
./tests/unit.test