From: Richard Purdie Date: Wed, 26 Feb 2014 11:35:43 +0000 (+0000) Subject: security-flags: Deal with powerpc build issues X-Git-Tag: lucaceresoli/bug-15201-perf-libtraceevent-missing~34376 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=4ef8f658874282ead0c46352474fdb03ad1f1038;p=thirdparty%2Fopenembedded%2Fopenembedded-core-contrib.git 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 --- diff --git a/meta/conf/distro/include/security_flags.inc b/meta/conf/distro/include/security_flags.inc index 93d635556ec..13711b05cb8 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