From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] valgrind: allow building on more ARM systems
Date: Wed, 1 Oct 2014 19:19:33 +0200 [thread overview]
Message-ID: <20141001191933.1b26e4ad@free-electrons.com> (raw)
In-Reply-To: <413cd7b6-4ed2-415b-8a6d-36f7148a6505@email.android.com>
Dear Thomas De Schampheleire,
On Wed, 01 Oct 2014 18:30:54 +0200, Thomas De Schampheleire wrote:
> >diff --git a/package/valgrind/valgrind.mk b/package/valgrind/valgrind.mk
> >index 24d0290..8bea031 100644
> >--- a/package/valgrind/valgrind.mk
> >+++ b/package/valgrind/valgrind.mk
> >@@ -17,7 +17,7 @@ VALGRIND_AUTORECONF = YES
> > # not. Therefore, we adjust the host tuple to specify we're on
> > # ARMv7. The valgrind package is guaranteed, through Config.in, to
> > # only be selected on Cortex A8 and Cortex A9 platforms.
> >-ifeq ($(BR2_cortex_a8)$(BR2_cortex_a9),y)
> >+ifeq ($(BR2_cortex_a5)$(BR2_cortex_a7)$(BR2_cortex_a8)$(BR2_cortex_a9)$(BR2_cortex_a12)$(BR2_cortex_a15),y)
> > VALGRIND_CONF_OPT += \
> > --host=$(patsubst arm-%,armv7-%,$(GNU_TARGET_NAME))
> > endif
>
> In fact, mips64+n32 abi is not supported, so I think
> this should be reflected too. I guess the same applies
> to the the le variant...
Right, but it's not an issue introduced by this new patch.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-10-01 17:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 15:15 [Buildroot] [PATCH] valgrind: allow building on more ARM systems Mike Williams
2014-10-01 16:14 ` Thomas Petazzoni
2014-10-01 16:30 ` Thomas De Schampheleire
2014-10-01 17:19 ` Thomas Petazzoni [this message]
2014-10-01 17:21 ` Thomas Petazzoni
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=20141001191933.1b26e4ad@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.