https://bugs.winehq.org/show_bug.cgi?id=48161
--- Comment #9 from Paul Gofman gofmanp@gmail.com --- I am not sure how exactly those different distributions builds are made, but if I add some additional flags using CFLAGS= variable for configure, those custom flags get added after the flags generated in configure script. So if -fcf-protection is there in CFLAGS= it will still take precedence.
Besides, unless I missed something, this change does not affect CROSS_CFLAGS, so mingw built libraries are unaffected by the change. I am afraid AION32 needs at least kernelbase.dll built without -fcf-protection, maybe something else.