The linker errors were found by a Zig user and I took up the challenge to fix it (original issue here: https://github.com/ziglang/zig/issues/9364)
Zig's using clang under the hood and on top of it, it adds automatic dynamic compilation of various libc implementations/bindings. For windows it dynamically builds .lib files from the mingw .def files as I understand (see https://github.com/ziglang/zig/blob/18b8738069268cc913bbae9580d2d170618a2ae9/src/mingw.zig#L277). It looks like it also builds .a files but ws2_32 seems to have been left out for some reason. On Thu, Jul 22, 2021 at 3:48 PM Martin Storsjö <[email protected]> wrote: > Hi, > > On Thu, 22 Jul 2021, Jonathan Marler wrote: > > > Yes I think the problem was with my environment. I had libws2_32.lib > > available but did not have libws2_32.a, so I was missing the symbols > coming > > from the source files in ming2-w64-crt. Thanks for the clarification. > > Hmm, ok, that's definitely your issue then. (Where do you get such a file > even - from the WinSDK? Because mingw-w64 itself doesn't produce any *.lib > files at all.) > > // Martin > _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
