From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] valgrind: Add support for MIPS architecture
Date: Sat, 29 Mar 2014 16:47:18 +0100 [thread overview]
Message-ID: <20140329164718.3b6af6c2@skate> (raw)
In-Reply-To: <1396025209-9495-1-git-send-email-Vincent.Riera@imgtec.com>
Dear Vicente Olivert Riera,
On Fri, 28 Mar 2014 16:46:49 +0000, Vicente Olivert Riera wrote:
> Reviewed-by: Markos Chandras <markos.chandras@imgtec.com>
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> ---
> package/valgrind/Config.in | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/package/valgrind/Config.in b/package/valgrind/Config.in
> index dacdd86..fd5649b 100644
> --- a/package/valgrind/Config.in
> +++ b/package/valgrind/Config.in
> @@ -1,7 +1,8 @@
> config BR2_PACKAGE_VALGRIND
> bool "valgrind"
> depends on BR2_i386 || BR2_x86_64 || BR2_cortex_a8 || \
> - BR2_cortex_a9 || BR2_powerpc
> + BR2_cortex_a9 || BR2_powerpc || BR2_mips || \
> + BR2_mipsel || BR2_mips64 || BR2_mips64el
> help
> Tool for debugging and profiling Linux programs.
This breaks the build on MIPS64:
http://autobuild.buildroot.org/results/213/21352bcbe1b309fef0f996c275cdfcda08619d96/build-end.log
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-03-29 15:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 16:46 [Buildroot] [PATCH] valgrind: Add support for MIPS architecture Vicente Olivert Riera
2014-03-28 18:16 ` Thomas De Schampheleire
2014-03-28 18:24 ` Vicente Olivert Riera
2014-03-28 18:40 ` Thomas De Schampheleire
2014-03-29 9:23 ` Thomas Petazzoni
2014-03-29 15:47 ` Thomas Petazzoni [this message]
2014-03-31 8:58 ` Vicente Olivert Riera
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=20140329164718.3b6af6c2@skate \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox