From: <Randy.MacLeod@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Cc: <raj.khem@gmail.com>
Subject: [PATCH 1/3] valgrind: make ptest depend on all components
Date: Mon, 12 Feb 2024 14:04:59 -0800 [thread overview]
Message-ID: <20240212220501.3571864-1-Randy.MacLeod@windriver.com> (raw)
From: Randy MacLeod <Randy.MacLeod@windriver.com>
When the helper scripts were split into separate packages, they
weren't added as ptest dependencies. Fix that.
Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com>
---
meta/recipes-devtools/valgrind/valgrind_3.21.0.bb | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/valgrind/valgrind_3.21.0.bb b/meta/recipes-devtools/valgrind/valgrind_3.21.0.bb
index 67a197c509..0903008e61 100644
--- a/meta/recipes-devtools/valgrind/valgrind_3.21.0.bb
+++ b/meta/recipes-devtools/valgrind/valgrind_3.21.0.bb
@@ -139,7 +139,9 @@ RDEPENDS:${PN}-ptest += " bash coreutils curl file \
perl-module-overloading perl-module-cwd perl-module-ipc-open3 \
perl-module-carp perl-module-symbol \
procps sed ${PN}-dbg ${PN}-src ${TCLIBC}-src gcc-runtime-dbg \
- util-linux-taskset"
+ util-linux-taskset \
+ ${PN}-cachegrind ${PN}-massif ${PN}-callgrind \
+"
RDEPENDS:${PN}-ptest:append:libc-glibc = " glibc-utils glibc-gconv-utf-32"
# One of the tests contains a bogus interpreter path on purpose.
--
2.43.0
next reply other threads:[~2024-02-12 22:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 22:04 Randy.MacLeod [this message]
2024-02-12 22:05 ` [PATCH 2/3] valgrind: update from 3.21.0 to 3.22.0 Randy.MacLeod
2024-02-13 2:40 ` Khem Raj
2024-02-14 0:23 ` Randy MacLeod
2024-02-14 1:07 ` Randy MacLeod
2024-02-12 22:05 ` [PATCH 3/3] valgrind: skip 14 ptests in 3.22 Randy.MacLeod
2024-02-14 13:51 ` [OE-core] " Richard Purdie
2024-02-15 1:40 ` 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=20240212220501.3571864-1-Randy.MacLeod@windriver.com \
--to=randy.macleod@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.