https://bugs.winehq.org/show_bug.cgi?id=55139
--- Comment #5 from aurb arusanu.bu@gmail.com --- Thanks David, your comment pointed me to test the stack-protection that turned out to be the culprit for Mageia. Once the stack-protector have been disabled no more errors and wine stack starts and runs as expected. This may work for OpenSuse too, as it uses stack-protector option too.(i.e. -fstack-protector-strong -fstack-clash-protection)
As an example, here is what was used for compilation of "loader/preloader.c" on Mageia:
gcc -m64 -c -o loader/preloader.o loader/preloader.c -Iloader -Iinclude -D__WINESRC__ -fno-builtin -DWINE_UNIX_LIB \ -fPIE -Wall -pipe -fcf-protection=none -fno-stack-protector -fno-strict-aliasing \ -Wdeclaration-after-statement -Wempty-body -Wignored-qualifiers -Winit-self \ -Wno-packed-not-aligned -Wshift-overflow=2 -Wstrict-prototypes -Wtype-limits \ -Wunused-but-set-parameter -Wvla -Wwrite-strings -Wpointer-arith -Wlogical-op -gdwarf-4 -O2 -g -pipe -Wformat -Werror=format-security -fstack-protector --param=ssp-buffer-size=4 -fasynchronous-unwind-tables -Wno-error
and removing/disabling "-fstack-protector --param=ssp-buffer-size=4" worked just fine.
This looks like a well known issue not quite a regression, sorry. Fedora seems to have had this workaround for some time now. At least for Mageia this works fine. Regards.