[OE-core] [PATCH 11/18] valgrind: fix buildpath QA issue
Hongxu Jia
hongxu.jia at windriver.com
Thu Mar 10 07:23:16 UTC 2016
- Pass DEBUG_FLAGS to SELECTED_OPTIMIZATION which fixes build
path issue in DWARF.
- It is hard to remove build path in ${PTEST_PATH}/drd/tests/
boost_thread. The reason is assert which has macro '__FILE__'
has been invoked in include file.(boost/thread/pthread/pthread_
mutex_scoped_lock.hpp)
[YOCTO #8457]
Signed-off-by: Hongxu Jia <hongxu.jia at windriver.com>
---
meta/recipes-devtools/valgrind/valgrind_3.11.0.bb | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb b/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb
index 7e23240..0afe014 100644
--- a/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb
+++ b/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb
@@ -49,8 +49,9 @@ EXTRA_OEMAKE = "-w"
# valgrind likes to control its own optimisation flags. It generally defaults
# to -O2 but uses -O0 for some specific test apps etc. Passing our own flags
-# (via CFLAGS) means we interfere with that.
-SELECTED_OPTIMIZATION = ""
+# (via CFLAGS) means we interfere with that. Only pass DEBUG_FLAGS to it
+# which fixes build path issue in DWARF.
+SELECTED_OPTIMIZATION = "${DEBUG_FLAGS}"
CFLAGS_append_libc-uclibc = " -D__UCLIBC__ "
--
1.9.1
More information about the Openembedded-core
mailing list