From: Saul Wold <sgw@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/4] linux-tools: don't build perf when GPLv3 in INCOMPATIBLE_LICENSE
Date: Tue, 24 Jan 2012 17:10:52 -0800 [thread overview]
Message-ID: <4F1F569C.1060703@linux.intel.com> (raw)
In-Reply-To: <CAMKF1sp+TWp_PneKg7P52GrytWqhcoyV+4=XU_=xk==jGQ9v3g@mail.gmail.com>
On 01/24/2012 05:04 PM, Khem Raj wrote:
> On Tue, Jan 24, 2012 at 3:59 PM, Saul Wold<sgw@linux.intel.com> wrote:
>>
>>
>> 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.
>
> is that a blocker for oe-core ?
>
It's a blocker for oe-core & 1.2, and we are not sure get can get the
refactor done by 1.2 given all the the other activities the team has, if
there are some external resources available o complete this work, that
would be very helpful!
Sau!
next prev parent reply other threads:[~2012-01-25 1:18 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 [this message]
2012-01-25 10:11 ` Andrei Gherzan
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=4F1F569C.1060703@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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.