From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH] task-core-tools-profile: fix valgrind for arm and systemtap for mips
Date: Wed, 8 Feb 2012 01:14:43 -0800 [thread overview]
Message-ID: <1328692483-4398-1-git-send-email-sgw@linux.intel.com> (raw)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
---
meta/recipes-core/tasks/task-core-tools-profile.bb | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/meta/recipes-core/tasks/task-core-tools-profile.bb b/meta/recipes-core/tasks/task-core-tools-profile.bb
index 254d3f5..30776ef 100644
--- a/meta/recipes-core/tasks/task-core-tools-profile.bb
+++ b/meta/recipes-core/tasks/task-core-tools-profile.bb
@@ -37,6 +37,7 @@ PROFILETOOLS = "\
# hence we exclude it from uclibc based builds
SYSTEMTAP = "systemtap"
SYSTEMTAP_libc-uclibc = ""
+SYSTEMTAP_mips = ""
# lttng-ust uses sched_getcpu() which is not there on uclibc
# for some of the architectures it can be patched to call the
@@ -53,6 +54,7 @@ LTTNGUST_mips = ""
VALGRIND = "valgrind"
VALGRIND_libc-uclibc = ""
VALGRIND_mips = ""
+VALGRIND_arm = ""
# exmap-console
# exmap-server
--
1.7.6.5
reply other threads:[~2012-02-08 9:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1328692483-4398-1-git-send-email-sgw@linux.intel.com \
--to=sgw@linux.intel.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