From: Andre McCurdy <armccurdy@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/3] valgrind: don't restrict to armv7a
Date: Tue, 22 Dec 2015 15:57:59 -0800 [thread overview]
Message-ID: <1450828680-662-3-git-send-email-armccurdy@gmail.com> (raw)
In-Reply-To: <1450828680-662-1-git-send-email-armccurdy@gmail.com>
Valgrind has been tested on armv5te/qemuarm, so it seems
that valgrind's configure check for armv7 is over cautious.
Signed-off-by: Andre McCurdy <armccurdy@gmail.com>
---
meta/recipes-devtools/valgrind/valgrind_3.11.0.bb | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb b/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb
index 3dc3cc1..bb3f6e1 100644
--- a/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb
+++ b/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb
@@ -26,14 +26,16 @@ SRC_URI = "http://www.valgrind.org/downloads/valgrind-${PV}.tar.bz2 \
SRC_URI[md5sum] = "4ea62074da73ae82e0162d6550d3f129"
SRC_URI[sha256sum] = "6c396271a8c1ddd5a6fb9abe714ea1e8a86fce85b30ab26b4266aeb4c2413b42"
-COMPATIBLE_HOST = '(i.86|x86_64|mips|powerpc|powerpc64).*-linux'
-COMPATIBLE_HOST_armv7a = 'arm.*-linux'
+COMPATIBLE_HOST = '(i.86|x86_64|arm|mips|powerpc|powerpc64).*-linux'
inherit autotools ptest
EXTRA_OECONF = "--enable-tls --without-mpicc"
-EXTRA_OECONF_armv7a = "--enable-tls -host=armv7-none-linux-gnueabi --without-mpicc"
EXTRA_OECONF += "${@['--enable-only32bit','--enable-only64bit'][d.getVar('SITEINFO_BITS', True) != '32']}"
+
+# valgrind checks host_cpu "armv7*)", so we need to over-ride the autotools.bbclass default --host option
+EXTRA_OECONF_append_arm = " --host=armv7${HOST_VENDOR}-${HOST_OS}"
+
EXTRA_OEMAKE = "-w"
do_install_append () {
--
1.9.1
next prev parent reply other threads:[~2015-12-22 23:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 23:57 [PATCH 0/3] valgrind fixes Andre McCurdy
2015-12-22 23:57 ` [PATCH 1/3] security_flags.inc: disable -fstack-protector-XXX for valgrind Andre McCurdy
2015-12-22 23:57 ` Andre McCurdy [this message]
2016-01-07 21:03 ` [PATCH 2/3] valgrind: don't restrict to armv7a Andre McCurdy
2016-01-07 21:39 ` Burton, Ross
2016-01-08 12:43 ` Alexander Kanavin
2015-12-22 23:58 ` [PATCH 3/3] valgrind: include aarch64 in COMPATIBLE_HOST Andre McCurdy
-- strict thread matches above, loose matches on Subject: below --
2016-01-08 14:57 [PATCH 0/3] Valgrind: update to 3.11.0 Alexander Kanavin
2016-01-08 14:57 ` [PATCH 2/3] valgrind: don't restrict to armv7a Alexander Kanavin
2016-01-13 2:13 ` dengke.du
2016-01-13 2:18 ` dengke.du
2016-01-13 3:23 ` Andre McCurdy
2016-01-13 5:00 ` Khem Raj
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=1450828680-662-3-git-send-email-armccurdy@gmail.com \
--to=armccurdy@gmail.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