From 4ef8f658874282ead0c46352474fdb03ad1f1038 Mon Sep 17 00:00:00 2001 From: Richard Purdie Date: Wed, 26 Feb 2014 11:35:43 +0000 Subject: security-flags: Deal with powerpc build issues Building powerpc machines with the standard security flags generated numerous build failures. Use a reduced set of flags for now to avoid linker issues and other compile failures. Signed-off-by: Richard Purdie --- meta/conf/distro/include/security_flags.inc | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/meta/conf/distro/include/security_flags.inc b/meta/conf/distro/include/security_flags.inc index 93d635556e..13711b05cb 100644 --- a/meta/conf/distro/include/security_flags.inc +++ b/meta/conf/distro/include/security_flags.inc @@ -2,6 +2,14 @@ SECURITY_CFLAGS ?= "-fstack-protector-all -pie -fpie -D_FORTIFY_SOURCE=2" SECURITY_NO_PIE_CFLAGS ?= "-fstack-protector-all -D_FORTIFY_SOURCE=2" SECURITY_LDFLAGS ?= "-Wl,-z,relro,-z,now" +# powerpc does not get on with pie for reasons not looked into as yet +SECURITY_CFLAGS_powerpc = "-fstack-protector-all -D_FORTIFY_SOURCE=2" +# Deal with ppc specific linker failures when using the cflags +SECURITY_CFLAGS_pn-dbus_powerpc = "" +SECURITY_CFLAGS_pn-dbus-ptest_powerpc = "" +SECURITY_CFLAGS_pn-libmatchbox_powerpc = "" +SECURITY_CFLAGS_pn-webkit-gtk_powerpc = "" + SECURITY_CFLAGS_pn-aspell = "${SECURITY_NO_PIE_CFLAGS}" SECURITY_CFLAGS_pn-beecrypt = "${SECURITY_NO_PIE_CFLAGS}" # Curl seems to check for FORTIFY_SOURCE in CFLAGS, but even assigned -- cgit 1.2.3-korg