summaryrefslogtreecommitdiffstats
path: root/meta/classes/gtk-immodules-cache.bbclass
diff options
context:
space:
mode:
authorAndre McCurdy <armccurdy@gmail.com>2015-12-22 15:57:58 -0800
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-01-07 13:40:15 +0000
commit3d19a1e10c52ef2db9ca32302c042267cdac1821 (patch)
treebd9b77f9f68afcf62618d2e41e811daab2405654 /meta/classes/gtk-immodules-cache.bbclass
parent807ed8a508a1665ad97bfea7ffe74879af0fd613 (diff)
downloadpoky-3d19a1e10c52ef2db9ca32302c042267cdac1821.tar.gz
security_flags.inc: disable -fstack-protector-XXX for valgrind
Valgrind (v3.11.0) expects to build with stack protection disabled and includes -fno-stack-protector in its default CFLAGS. However, the CFLAGS provided by OE are included on the compiler command line after the defaults so any -fstack-protector-all / -fstack-protector-strong option provided by security_flags.inc will cause problems. | .../build-bcm97425vms/tmp/work/mips32el-rdk-linux/valgrind/3.11.0-r0/valgrind-3.11.0/coregrind/m_mallocfree.c:892: undefined reference to `__stack_chk_guard' | .../build-bcm97425vms/tmp/work/mips32el-rdk-linux/valgrind/3.11.0-r0/valgrind-3.11.0/coregrind/m_mallocfree.c:947: undefined reference to `__stack_chk_fail' (From OE-Core rev: ff4f46700a4810fcb49c58978b17af4f52fa9925) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/classes/gtk-immodules-cache.bbclass')
0 files changed, 0 insertions, 0 deletions