From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v3] valgrind: Enable valgrind for armv7
Date: Thu, 24 May 2012 11:14:56 -0700 [thread overview]
Message-ID: <4FBE7AA0.6090705@linux.intel.com> (raw)
In-Reply-To: <1337780788-30178-1-git-send-email-s.stirtzel@googlemail.com>
On 05/23/2012 06:46 AM, Samuel Stirtzel wrote:
> Valgrind supports the armv7 architecture, this patch allows armv7 users to build and use Valgrind
>
> This patch was run-tested on a Gumstix Overo (armv7a cortex-a8)
> * The test consisted of running valgrinds memcheck (memory leakage detection),
> * and callgrind (profiling) on a Qt 4 application
>
> Signed-off-by: Samuel Stirtzel<s.stirtzel@googlemail.com>
> ---
> meta/recipes-devtools/valgrind/valgrind_3.7.0.bb | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/meta/recipes-devtools/valgrind/valgrind_3.7.0.bb b/meta/recipes-devtools/valgrind/valgrind_3.7.0.bb
> index d7c7b24..6b54472 100644
> --- a/meta/recipes-devtools/valgrind/valgrind_3.7.0.bb
> +++ b/meta/recipes-devtools/valgrind/valgrind_3.7.0.bb
> @@ -23,13 +23,16 @@ SRC_URI[md5sum] = "a855fda56edf05614f099dca316d1775"
> SRC_URI[sha256sum] = "5d62c0330f1481fe2c593249192fa68ff454c19c34343978cc9ce91aa324cbf6"
>
> COMPATIBLE_HOST = '(i.86|x86_64|powerpc|powerpc64).*-linux'
> +COMPATIBLE_HOST_armv7a = 'arm.*-linux'
>
> inherit autotools
>
> EXTRA_OECONF = "--enable-tls"
> +EXTRA_OECONF_armv7a = "--enable-tls -host=armv7-none-linux-gnueabi"
> EXTRA_OEMAKE = "-w"
> PARALLEL_MAKE = ""
>
> FILES_${PN}-dbg += "${libdir}/${PN}/*/.debug/*"
> RRECOMMENDS_${PN}_powerpc += "${TCLIBC}-dbg"
> RRECOMMENDS_${PN}_powerpc64 += "${TCLIBC}-dbg"
> +RRECOMMENDS_${PN}_armv7a += "${TCLIBC}-dbg"
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2012-05-24 18:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 13:46 [PATCH v3] valgrind: Enable valgrind for armv7 Samuel Stirtzel
2012-05-24 18:14 ` Saul Wold [this message]
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=4FBE7AA0.6090705@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 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.