Comment 1 for bug 2028276

[09:24:34] <eMTee> https://sourceforge.net/p/mingw-w64/mailman/message/36804945/ "* __FORTIFY_SOURCE support "
[09:40:16] <eMTee> https://github.com/StephanTLavavej/mingw-distro/issues/71 , https://github.com/msys2/MINGW-packages/issues/5803
[11:39:11] <eMTee> meh, it's not because of these. I tried '-fstack-check=no', '-fno-stack-check', '-fno-stack-protector', '-fno-stack-clash-protection', '-D_FORTIFY_SOURCE=0' , still errors

[14:16:20] <eMTee> managed to compile it by adding 'BufferOverflowU' lib from the SDK. Altough some fix it by using dummy defines like https://github.com/kfrlib/fft-benchmark/blob/master/mingw_fix.h
I tried

extern "C" {
   int __security_cookie;
}

with no luck, not sure if I added it to the proper place though.

[14:17:37] <eMTee> I still want to know what option to disable or what was enabled vs. the old 8.1 build we've been using but I'm at a loss how to find it out what it is.
[14:18:39] <eMTee> Nevertheless these checks should make the app more safe, not sure to what extent though since it's a 20 year old technology/practice.

Will try a similar winlibs built compiler which reportedly don't exhibit this issue with its defaults.