From: Randy MacLeod <Randy.MacLeod@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 2/5] valgrind: do not strip the package or ptests
Date: Mon, 13 May 2019 23:57:13 -0400 [thread overview]
Message-ID: <20190514035716.27376-2-Randy.MacLeod@windriver.com> (raw)
In-Reply-To: <20190514035716.27376-1-Randy.MacLeod@windriver.com>
About half the ptests will fail if the executables deployed
as part of the ptest package are stripped. Currently
there is no easy way to only strip the main valgrind
package so leave it and the ptests *all* unstripped.
There is an enhancement filed to enable wildcard stripping:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13343
so this recipe can be fixed once that is implemented.
Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com>
---
meta/recipes-devtools/valgrind/valgrind_3.15.0.bb | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/meta/recipes-devtools/valgrind/valgrind_3.15.0.bb b/meta/recipes-devtools/valgrind/valgrind_3.15.0.bb
index 9749fdb244..b72f4d76ee 100644
--- a/meta/recipes-devtools/valgrind/valgrind_3.15.0.bb
+++ b/meta/recipes-devtools/valgrind/valgrind_3.15.0.bb
@@ -114,6 +114,10 @@ RDEPENDS_${PN}-ptest_append_libc-glibc = " glibc-utils"
# One of the tests contains a bogus interpreter path on purpose.
# Skip file dependency check
SKIP_FILEDEPS_${PN}-ptest = '1'
+# INHIBIT_PACKAGE_STRIP_${PN}-ptest = '1'
+# PACKAGE_DEBUG_SPLIT_STYLE_${PN}-ptest = 'debug-file-directory'
+INHIBIT_PACKAGE_STRIP = '1'
+PACKAGE_DEBUG_SPLIT_STYLE = 'debug-file-directory'
do_compile_ptest() {
oe_runmake check
--
2.17.0
next prev parent reply other threads:[~2019-05-14 3:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 3:57 [PATCH 1/5] valgrind: fix vg_regtest return code Randy MacLeod
2019-05-14 3:57 ` Randy MacLeod [this message]
2019-05-14 14:08 ` [PATCH 2/5] valgrind: do not strip the package or ptests Richard Purdie
2019-05-14 17:54 ` Randy MacLeod
2019-05-14 21:32 ` richard.purdie
2019-05-14 21:42 ` Randy MacLeod
2019-05-14 21:46 ` richard.purdie
2019-05-15 2:22 ` Randy MacLeod
2019-05-15 19:11 ` Randy MacLeod
2019-05-20 21:15 ` Khem Raj
2019-05-15 1:17 ` Mittal, Anuj
2019-05-20 20:52 ` Khem Raj
2019-05-14 16:44 ` Burton, Ross
2019-05-14 3:57 ` [PATCH 3/5] valgrind: update the ptest subdirs list Randy MacLeod
2019-05-14 3:57 ` [PATCH 4/5] valgrind: adjust test filters and expected output Randy MacLeod
2019-05-14 3:57 ` [PATCH 5/5] valgrind: fix call/cachegrind ptests Randy MacLeod
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190514035716.27376-2-Randy.MacLeod@windriver.com \
--to=randy.macleod@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox