From: Andrei Gherzan <andrei@gherzan.ro>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/4] linux-tools: don't build perf when GPLv3 in INCOMPATIBLE_LICENSE
Date: Wed, 25 Jan 2012 12:11:21 +0200 [thread overview]
Message-ID: <4F1FD549.7040708@gherzan.ro> (raw)
In-Reply-To: <4F1F45F0.208@linux.intel.com>
On 01/25/2012 01:59 AM, Saul Wold wrote:
> On 01/24/2012 03:42 PM, Khem Raj wrote:
>> On Tue, Jan 24, 2012 at 3:26 PM, Joshua Lock<josh@linux.intel.com>
>> wrote:
>>> Long term we should look at moving perf to a separate recipe but as a
>>> short term solution this patch will ensure that when GPLv3 is in
>>
>> would I be asking too much to do that instead of this patch :)
>> I think it will be good thing in general since other layers
>> now have to define these tasks if they inherit from oe-core kernel
>> class.
>>
> Khem,
>
> The issue is timing and resources to do this work, it a larger task
> that may take more than a few days to refactor perf into it's own
> recipe and share the source area (ala work-shared/gcc). We need to
> get the non-GPLv3 build working again and this seems like the most
> direct route to accomplish that.
>
> Sau!
>
This is a good workaround for this bug. Obviously a "refactor way" would
be a better one in my opinion too. But for now, as this bug breaks a
non-GPLv3 build, a fast solution, like this, is needed.
@g
next prev parent reply other threads:[~2012-01-25 10:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 23:26 [PATCH 0/4] Various updates Joshua Lock
2012-01-24 23:26 ` [PATCH 1/4] clutter-gst: update to 1.4.6 Joshua Lock
2012-01-24 23:26 ` [PATCH 2/4] linux-tools: don't build perf when GPLv3 in INCOMPATIBLE_LICENSE Joshua Lock
2012-01-24 23:42 ` Khem Raj
2012-01-24 23:59 ` Saul Wold
2012-01-25 1:04 ` Khem Raj
2012-01-25 1:10 ` Saul Wold
2012-01-25 10:11 ` Andrei Gherzan [this message]
2012-01-25 12:31 ` Richard Purdie
2012-01-24 23:26 ` [PATCH 3/4] cogl: update upstream status for build_for_armv4t.patch Joshua Lock
2012-01-24 23:26 ` [PATCH 4/4] distro-tracking-fields: update entries for clutter-gst-1.8 Joshua Lock
2012-01-25 14:34 ` [PATCH 0/4] Various updates 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=4F1FD549.7040708@gherzan.ro \
--to=andrei@gherzan.ro \
--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