From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: darren.hart@intel.com, openembedded-core@lists.openembedded.org
Subject: Re: [discussion] perf: specify SLANG_INC dir for perf
Date: Thu, 16 Aug 2012 12:00:35 -0400 [thread overview]
Message-ID: <502D1923.2030502@windriver.com> (raw)
In-Reply-To: <1345132684.14667.70.camel@ted>
On 12-08-16 11:58 AM, Richard Purdie wrote:
> On Thu, 2012-08-16 at 11:33 -0400, Bruce Ashfield wrote:
>> On 12-08-13 10:17 PM, Liang Li wrote:
>>> Hi Richard,
>>>
>>> Ping ...
>>>
>>> Hopefully you could recall sufficient context from this thread about
>>> the 'include path for slang.h' cause compile error issue that we are
>>> trying to fix here.
>>
>> Bump.
>>
>> I'm holding off on merging a kernel patch for this while this is still
>> outstanding.
>>
>> Can I distill this into the following (in the hope of resolving it).
>>
>> - do we want to fix this problem for all kernels, or just the linux-yocto
>> ones ? And by 'fix', I mean without the requirement of porting
>> a kernel patch to older recipes.
>
> I propose we add a sed expression to the general kernel do_install which
> changes the -I/usr/include/slang -> -I=/usr/include/slang. That should
> be generic, acceptable to upstream and fixes all kernel versions.
That'll work as well, as long as it is captured in the staging directory
perf will build.
As long as we construct it to check before sed'ing (is that a verb), it'll
adapt to kernels that do and don't have a patch already.
Liang and I can take care of putting something together. Does that work
for you ?
Cheers,
Bruce
>
> Comments?
>
> Cheers,
>
> Richard
>
next prev parent reply other threads:[~2012-08-16 16:12 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 15:43 [PATCH] perf: pass STAGING_INCDIR(sysroot) to perf Liang Li
2012-08-07 12:56 ` Bruce Ashfield
2012-08-07 14:12 ` Richard Purdie
2012-08-07 14:19 ` Bruce Ashfield
2012-08-07 14:27 ` Richard Purdie
2012-08-07 14:02 ` Richard Purdie
2012-08-07 14:07 ` Bruce Ashfield
2012-08-07 14:22 ` Richard Purdie
2012-08-07 14:29 ` Bruce Ashfield
2012-08-07 14:44 ` Richard Purdie
2012-08-07 15:26 ` Bruce Ashfield
2012-08-07 15:41 ` Richard Purdie
2012-08-07 15:54 ` Bruce Ashfield
2012-08-07 16:02 ` Richard Purdie
2012-08-08 3:37 ` Liang Li
2012-08-09 0:36 ` Darren Hart
2012-08-09 1:24 ` Liang Li
2012-08-09 1:41 ` Darren Hart
2012-08-09 1:52 ` Liang Li
2012-08-09 3:54 ` Darren Hart
2012-08-09 1:33 ` Bruce Ashfield
2012-08-14 2:17 ` [discussion] perf: specify SLANG_INC dir for perf Liang Li
2012-08-16 15:33 ` Bruce Ashfield
2012-08-16 15:58 ` Richard Purdie
2012-08-16 16:00 ` Bruce Ashfield [this message]
2012-08-16 16:12 ` McClintock Matthew-B29882
2012-08-17 3:32 ` Liang Li
2012-08-17 9:35 ` Richard Purdie
2012-08-17 10:00 ` Liang Li
2012-08-17 10:53 ` Richard Purdie
2012-08-17 12:55 ` Bruce Ashfield
2012-08-17 13:01 ` Liang Li
2012-08-17 13:05 ` Liang Li
2012-08-20 14:48 ` Bruce Ashfield
2012-08-21 5:08 ` Liang Li
2012-08-21 8:51 ` Henning Heinold
2012-08-21 9:19 ` Liang Li
2012-08-21 10:40 ` Richard Purdie
2012-08-21 13:07 ` Bruce Ashfield
2012-08-22 3:01 ` Liang Li
2012-08-22 5:41 ` Bruce Ashfield
2012-08-22 8:17 ` Liang Li
2012-08-17 14:35 ` Darren Hart
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=502D1923.2030502@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=darren.hart@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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