security_flags: eliminate FORTIFY_SOURCE for debug builds
If -D_FORTIFY_SOURCE=2 is included in CFLAGS for debug builds, many warnings will be generated and some packages will fail to build. So, only conditionally include it. (From OE-Core rev: 1b576012a6a2b2ebc2c507cdaebd62174810b191) Signed-off-by: Joe Slater <jslater@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
c4437f1780
commit
abe6459c28
|
@ -5,13 +5,18 @@
|
|||
# From a Yocto Project perspective, this file is included and tested
|
||||
# in the DISTRO="poky-lsb" configuration.
|
||||
|
||||
SECURITY_CFLAGS ?= "-fstack-protector-all -pie -fpie -D_FORTIFY_SOURCE=2"
|
||||
SECURITY_NO_PIE_CFLAGS ?= "-fstack-protector-all -D_FORTIFY_SOURCE=2"
|
||||
# _FORTIFY_SOURCE requires -O1 or higher, so disable in debug builds as they use
|
||||
# -O0 which then results in a compiler warning.
|
||||
lcl_maybe_fortify = "${@base_conditional('DEBUG_BUILD','1','','-D_FORTIFY_SOURCE=2',d)}"
|
||||
|
||||
SECURITY_CFLAGS ?= "-fstack-protector-all -pie -fpie ${lcl_maybe_fortify}"
|
||||
SECURITY_NO_PIE_CFLAGS ?= "-fstack-protector-all ${lcl_maybe_fortify}"
|
||||
|
||||
SECURITY_LDFLAGS ?= "-Wl,-z,relro,-z,now"
|
||||
SECURITY_X_LDFLAGS ?= "-Wl,-z,relro"
|
||||
|
||||
# powerpc does not get on with pie for reasons not looked into as yet
|
||||
SECURITY_CFLAGS_powerpc = "-fstack-protector-all -D_FORTIFY_SOURCE=2"
|
||||
SECURITY_CFLAGS_powerpc = "-fstack-protector-all ${lcl_maybe_fortify}"
|
||||
# Deal with ppc specific linker failures when using the cflags
|
||||
SECURITY_CFLAGS_pn-dbus_powerpc = ""
|
||||
SECURITY_CFLAGS_pn-dbus-ptest_powerpc = ""
|
||||
|
|
Loading…
Reference in New Issue