Patchwork security-flags: Avoid lttng-tools issue on arm

login
register
mail settings
Submitter Richard Purdie
Date Feb. 26, 2014, 1:40 p.m.
Message ID <1393422041.31769.112.camel@ted>
Download mbox | patch
Permalink /patch/67469/
State New
Headers show

Comments

Richard Purdie - Feb. 26, 2014, 1:40 p.m.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
Phil Blundell - Feb. 26, 2014, 1:59 p.m.
On Wed, 2014-02-26 at 13:40 +0000, Richard Purdie wrote:
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

Can you provide more details of what the issue that you're avoiding
actually is?

p.

Patch

diff --git a/meta/conf/distro/include/security_flags.inc b/meta/conf/distro/include/security_flags.inc
index b5489d8..51cc38e 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 = ""
 
+# 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