Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] eglibc: package mtrace separately
Date: Fri, 27 Apr 2012 22:48:24 +0100	[thread overview]
Message-ID: <1335563304.20130.114.camel@ted> (raw)
In-Reply-To: <4F9ABCEC.60403@linux.intel.com>

On Fri, 2012-04-27 at 08:36 -0700, Saul Wold wrote:
> On 04/26/2012 03:53 PM, nitin.a.kamble@intel.com wrote:
> > From: Nitin A Kamble<nitin.a.kamble@intel.com>
> >
> > And install it only for nativesdk images
> >
> I think this needs to be in the -sdk images also, not just nativesdk.

Why? Do we need mtrace in the nativesdk?

I'm not sure why we're adding this.

Cheers,

Richard




  parent reply	other threads:[~2012-04-27 21:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26 22:53 [PATCH 0/2] Misc fixes nitin.a.kamble
2012-04-26 22:53 ` [PATCH 1/2] eglibc: package mtrace separately nitin.a.kamble
2012-04-27 15:36   ` Saul Wold
2012-04-27 16:24     ` Kamble, Nitin A
2012-04-27 21:48     ` Richard Purdie [this message]
2012-04-27 21:52     ` Richard Purdie
2012-04-30 15:14       ` Kamble, Nitin A
2012-05-01 19:44         ` Richard Purdie
2012-04-26 22:53 ` [PATCH 2/2] tcl: fix target recipe build issue on older distros nitin.a.kamble
2012-05-01 18:32 ` [PATCH 0/2] Misc fixes Saul Wold
  -- strict thread matches above, loose matches on Subject: below --
2012-05-16 18:11 nitin.a.kamble
2012-05-16 18:11 ` [PATCH 1/2] eglibc: package mtrace separately nitin.a.kamble
2012-05-16 18:33   ` Saul Wold
2012-05-16 19:45     ` Kamble, Nitin A

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=1335563304.20130.114.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --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