From 5ab9d7e28f987fba8bab03bb7851c263f746c208 Mon Sep 17 00:00:00 2001 From: Richard Purdie Date: Wed, 26 Feb 2014 13:40:41 +0000 Subject: [PATCH] security-flags: Avoid lttng-tools issue on arm (From OE-Core rev: 010d5b437413156c3f4dc90a14698231bb195c2e) Signed-off-by: Richard Purdie --- meta/conf/distro/include/security_flags.inc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/meta/conf/distro/include/security_flags.inc b/meta/conf/distro/include/security_flags.inc index 13711b05cb8..a871a3fe0fc 100644 --- a/meta/conf/distro/include/security_flags.inc +++ b/meta/conf/distro/include/security_flags.inc @@ -10,6 +10,9 @@ SECURITY_CFLAGS_pn-dbus-ptest_powerpc = "" SECURITY_CFLAGS_pn-libmatchbox_powerpc = "" SECURITY_CFLAGS_pn-webkit-gtk_powerpc = "" +# arm specific security flag issues +SECURITY_CFLAGS_pn-lttng-tools_arm = "${SECURITY_NO_PIE_CFLAGS}" + 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 -- 2.47.3