From: Saul Wold <sgw@linux.intel.com>
To: Jack Mitchell <ml@communistcode.co.uk>
Cc: Jack Mitchell <jack.mitchell@dbbroadcast.co.uk>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCHv2] local.conf.sample: change valgrind support architecture comment
Date: Wed, 19 Sep 2012 10:39:10 -0700 [thread overview]
Message-ID: <505A033E.3060107@linux.intel.com> (raw)
In-Reply-To: <1347539241-594-1-git-send-email-ml@communistcode.co.uk>
On 09/13/2012 05:27 AM, Jack Mitchell wrote:
> From: Jack Mitchell <jack.mitchell@dbbroadcast.co.uk>
>
> The comment for debug-tools states valgrind will only be installed for x86
> targets. This is not true as valgrind now supports x86*, PPC* and ARMv7a;
> delete the comment as the architecture support is now so varied.
>
> Signed-off-by: Jack Mitchell <jack.mitchell@dbbroadcast.co.uk>
> ---
> meta/conf/local.conf.sample | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/conf/local.conf.sample b/meta/conf/local.conf.sample
> index 5679c03..04d947f 100644
> --- a/meta/conf/local.conf.sample
> +++ b/meta/conf/local.conf.sample
> @@ -119,7 +119,7 @@ PACKAGE_CLASSES ?= "package_ipk"
> # (useful if you want to develop against libs in the image)
> # "tools-sdk" - add development tools (gcc, make, pkgconfig etc.)
> # "tools-debug" - add debugging tools (gdb, strace)
> -# "tools-profile" - add profiling tools (oprofile, exmap, lttng valgrind (x86 only))
> +# "tools-profile" - add profiling tools (oprofile, exmap, lttng, valgrind)
> # "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.)
> # "debug-tweaks" - make an image suitable for development
> # e.g. ssh root access has a blank password
>
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2012-09-19 17:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 11:20 [PATCH] local.conf.sample: change valgrind support architecture comment Jack Mitchell
2012-09-13 12:21 ` Paul Eggleton
2012-09-13 12:27 ` [PATCHv2] " Jack Mitchell
2012-09-19 17:39 ` 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=505A033E.3060107@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=jack.mitchell@dbbroadcast.co.uk \
--cc=ml@communistcode.co.uk \
--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