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.
Giving valgrind control of optimisation is hopefully an even better
solution than the previous one of forcing -O0 for all tests.
http://git.openembedded.org/openembedded-core/commit/?h=master-next&id=
98c4a3ffb8dca10739be600e8d6df7fb6aa4958f
Signed-off-by: Andre McCurdy <armccurdy@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
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 = ""
+
CFLAGS_append_libc-uclibc = " -D__UCLIBC__ "
do_install_append () {
INSANE_SKIP_${PN}-ptest += "file-rdeps"
do_compile_ptest() {
- oe_runmake check CFLAGS="${CFLAGS} -O0" CXXFLAGS="${CXXFLAGS} -O0"
+ oe_runmake check
}
-
do_install_ptest() {
chmod +x ${B}/tests/vg_regtest
# handle multilib
sed -i s:@libdir@:${libdir}:g ${D}${PTEST_PATH}/run-ptest
}
-