#Fontforge mingw Patch#

I'll start off by saying that building with a 32-bit target works fine. I can't say that I understand much of how gnulib acutually works, so forgive me if this is a basic error. Up until a few months ago, everything was building fine, but now I'm facing an issue which I believe has to do with Gnulib. I've been having some difficulty building FontForge on Windows (8.1 64bit) using msys2 and mingw-w64 (64-bit target).

#Fontforge mingw Patch#

The patch works for me, but I know practically nothing about m4, so I have no idea if I'm doing the right thing or not. I have attached a patch to gethostname.m4 which reorders the check - if Winsock is found, try to compile by linking to it first. Which means that this check succeeds when it should not. > x86_64-w64-mingw32-gcc -std=gnu99 -std=gnu99 -o conftest.exe -DWIN32 -I/home/tanjj/ffbuild/target/mingw64//include -I/mingw64/include -I/usr/local/include -I/include -g -DWIN32 -I/home/tanjj/ffbuild/target/mingw64//include -I/mingw64/include -I/usr/local/include -I/include -g -I$ -L/home/tanjj/ffbuild/target/mingw64//lib -L/mingw64/lib -L/usr/local/lib -L/lib -lws2_32 conftest.c -lX11 -lltdl -lws2_32 >&5 Now, normally this check will fail (at linking), BUT since a check has been made before for linking to X11 (which links to ws2_32), ws2_32 is being implicitly linked: Note that unistd.h includes winsock2.h on my platform. What was happening is that in the check for `gethostname`, it tries to compile without linking against ws2_32.