From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] linux-tools: don't build perf when GPLv3 in INCOMPATIBLE_LICENSE
Date: Wed, 25 Jan 2012 17:10:20 -0800 [thread overview]
Message-ID: <4F20A7FC.2090603@linux.intel.com> (raw)
In-Reply-To: <CAMKF1sropDJF5Su71dHZ=NGsQMOmcU=iXezwXYuJA=NX_6=c1g@mail.gmail.com>
On 25/01/12 15:55, Khem Raj wrote:
> On Wed, Jan 25, 2012 at 3:05 PM, Joshua Lock<josh@linux.intel.com> wrote:
>> -PERFDEPENDS_libc-uclibc = ""
>> PERFRDEPENDS = "python perl elfutils"
>> -PERFRDEPENDS_libc-uclibc = ""
>
> now how will PERFDEPENDS be cleared for uclibc ?
Whoops, little over zealous there... Updated patch in the same place.
Cheers,
Joshua
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-01-26 1:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 23:05 [PATCH 0/1] Don't add binutils to images when GPLv3 in INCOMPATIBLE_LICENSE v2 Joshua Lock
2012-01-25 23:05 ` [PATCH 1/1] linux-tools: don't build perf when GPLv3 in INCOMPATIBLE_LICENSE Joshua Lock
2012-01-25 23:55 ` Khem Raj
2012-01-26 1:10 ` Joshua Lock [this message]
2012-01-26 20:48 ` [PATCH 0/1] Don't add binutils to images when GPLv3 in INCOMPATIBLE_LICENSE v2 Richard Purdie
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=4F20A7FC.2090603@linux.intel.com \
--to=josh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox