Don't use -fstack-protector-strong when compiling for Windows

Initial motivation of adding the flag was better consistency with
compile flags used for regular Arch Linux packages.

However, adding -fstack-protector-strong seems to cause segmentation
faults even before main() is called.

The issue is not reproducible with a simple hello world app and also
not reproducible when launching the app under Linux with WINE. But
a full-blown Qt 5 app crashes in the way described.
This commit is contained in:
Martchus 2019-01-05 01:47:00 +01:00
parent 9d553d2af7
commit f0175878db
4 changed files with 4 additions and 4 deletions

View File

@ -1,7 +1,7 @@
pkgname=mingw-w64-cmake
pkgver=1
pkgrel=23.1
pkgrel=23.2
arch=('any')
pkgdesc="CMake wrapper for MinGW (mingw-w64)"
depends=('cmake' 'mingw-w64-gcc' 'mingw-w64-pkg-config')

View File

@ -4,7 +4,7 @@ mingw_prefix=/usr/@TRIPLE@
export PKG_CONFIG_LIBDIR="${mingw_prefix}/lib/pkgconfig"
default_mingw_pp_flags="-D_FORTIFY_SOURCE=2"
default_mingw_compiler_flags="$default_mingw_pp_flags -O2 -pipe -fstack-protector-strong -fno-plt -fexceptions --param=ssp-buffer-size=4"
default_mingw_compiler_flags="$default_mingw_pp_flags -O2 -pipe -fno-plt -fexceptions --param=ssp-buffer-size=4"
default_mingw_linker_flags="-Wl,-O1,--sort-common,--as-needed"
export CPPFLAGS="${MINGW_CPPFLAGS:-$default_mingw_pp_flags $CPPFLAGS}"

View File

@ -1,7 +1,7 @@
pkgname=mingw-w64-configure
pkgver=0.1.1
pkgrel=2.1
pkgrel=2.2
arch=(any)
pkgdesc="configure wrapper for MinGW (mingw-w64)"
depends=('mingw-w64-gcc' 'mingw-w64-pkg-config')

View File

@ -9,7 +9,7 @@ else
fi
default_mingw_pp_flags="-D_FORTIFY_SOURCE=2"
default_mingw_compiler_flags="-O2 -pipe -fstack-protector-strong -fno-plt -fexceptions --param=ssp-buffer-size=4"
default_mingw_compiler_flags="-O2 -pipe -fno-plt -fexceptions --param=ssp-buffer-size=4"
default_mingw_linker_flags="-Wl,-O1,--sort-common,--as-needed"
export CPPFLAGS="${MINGW_CPPFLAGS:-$default_mingw_pp_flags $CPPFLAGS}"