etc/defaults.conf: move _FORTIFY_SOURCE to CFLAGS.
Lots of pkgs seem to fail when _FORTIFY_SOURCE is defined in CPPFLAGS due to a missing optimization level, and also some of them simply ignore CPPFLAGS, therefore move it to CFLAGS to fix this once and for all.
This commit is contained in:
parent
c645a1c097
commit
4c49a35f43
1 changed files with 1 additions and 2 deletions
|
@ -24,9 +24,8 @@ XBPS_INSTALL_ARGS="--repository=http://repo.voidlinux.eu/current"
|
||||||
# Native Compilation/Preprocessor flags for C and C++. Additional settings
|
# Native Compilation/Preprocessor flags for C and C++. Additional settings
|
||||||
# for the target architecture are also declared in common/build-profiles/<arch>.sh.
|
# for the target architecture are also declared in common/build-profiles/<arch>.sh.
|
||||||
#
|
#
|
||||||
XBPS_CFLAGS="-O2 -pipe -fstack-protector-strong"
|
XBPS_CFLAGS="-O2 -pipe -fstack-protector-strong -D_FORTIFY_SOURCE=2"
|
||||||
XBPS_CXXFLAGS="${XBPS_CFLAGS}"
|
XBPS_CXXFLAGS="${XBPS_CFLAGS}"
|
||||||
XBPS_CPPFLAGS="-D_FORTIFY_SOURCE=2"
|
|
||||||
|
|
||||||
# [OPTIONAL]
|
# [OPTIONAL]
|
||||||
# Linker flags passed to the compiler. By default we use --as-needed to
|
# Linker flags passed to the compiler. By default we use --as-needed to
|
||||||
|
|
Loading…
Reference in a new issue