From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Liang Li <liang.li@windriver.com>
Cc: darren.hart@intel.com, openembedded-core@lists.openembedded.org
Subject: Re: [discussion] perf: specify SLANG_INC dir for perf
Date: Fri, 17 Aug 2012 11:53:02 +0100 [thread overview]
Message-ID: <1345200782.26132.18.camel@ted> (raw)
In-Reply-To: <20120817100001.GA16621@localhost>
On Fri, 2012-08-17 at 18:00 +0800, Liang Li wrote:
> I am totally confused, you mentioned 'general kernel do_install', I
> assume it's oe-core kernel.bbclass concept. Then you mentioned 'get
> the fix upstream in the mainline kernel', how could that happen?
>
> We are discussing about the solution to 'fix the compile warning to
> error' stuff that triggered by the '-I/usr/include/slang', right?
Yes.
> We do not necessarily have to change recipe to fix it since the issue
> is not introduced by the recipe, the hard coded '-I/usr/include/slang'
> in the Makefile cause the issue, we can fix the root cause by kernel
> patch(other than just comment the line out). I see your previous patch
> to kernel, by comment out the '-I/usr/include/slang' line in the
> Makefile, is the same behavior, but we won't have the change(comment
> out -I.. in Makefile) upstream to mainline, right?
I am suggesting that firstly, someone send a patch to the mainline
kernel which changes -I/usr/include/slang to -I=/usr/include/slang in
that Makefile.
Secondly, I'm suggesting that we add a line to kernel_do_install() in
kernel.bbclass which does a sed on the Makefile as installed into
$kerneldir which changes -I/usr/include/slang to -I=/usr/include/slang.
We can then drop the patch I added to the linux-yocto kernels.
This is all that should be needed, it should fix all the issues people
have reported in a way that is acceptable to everyone.
Cheers,
Richard
next prev parent reply other threads:[~2012-08-17 11:05 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
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 [this message]
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=1345200782.26132.18.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=darren.hart@intel.com \
--cc=liang.li@windriver.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