"...with mingw-w64 if you define _FORTIFY_SOUECE to something
greater than zero you have to link against libssp, either by adding
-fstack-protector or -lssp, because mingw-w64, unlike GNU libc, does
not provide fortified functions."
https://github.com/msys2/MINGW-packages/issues/5868
The previous update[1] left the patch in a state where it was applying
the same changeset twice with an incorrect commit message[2] for patch 2
[1] 8ed36bf81f
[2] 8ed36bf81f/src/mingw-w64-1.patch
"...with mingw-w64 if you define _FORTIFY_SOUECE to something
greater than zero you have to link against libssp, either by adding
-fstack-protector or -lssp, because mingw-w64, unlike GNU libc, does
not provide fortified functions."
https://github.com/msys2/MINGW-packages/issues/5868
In the patch that is now in MXE, somehow the line numbers got
messed up. The result is that the XMLPUBVAR is now fixed for
the cygwin case, not for mingw. This patch fixes that. It adds
'extern' to the __declspec(dllexport) definition of XMLPUBVAR.
This is also what is already in upstream libxml2, including in the
version that is shipped with mxe. See:
1eabc31401
Multiple defintiions for some symbols such as PC are introduced
by readline and termcap. This causes GCC 10 linking error.
Related to:
Default to -fno-common
https://gcc.gnu.org/gcc-10/porting_to.html
Tony Theodore
Mark Brand
Alexandros Theodotou
Lothar Serra Mari
Jan-Michael Brummer
Tibor Lajos Füzi
jan
Jonas Kvinge