From: Darren Hart <dvhart@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
Subject: Re: [PATCH] perf-3.4: fix hardcoded slang include dir
Date: Thu, 02 Aug 2012 12:53:26 -0700 [thread overview]
Message-ID: <501ADAB6.5030004@linux.intel.com> (raw)
In-Reply-To: <50174FD1.6020805@windriver.com>
On 07/30/2012 08:24 PM, Rongqing Li wrote:
>
>
> On 2012年07月30日 17:43, Enrico Scholz wrote:
>> <rongqing.li-CWA4WttNNZF54TAoqtyWWQ@public.gmane.org> writes:
>>
>>> +++ b/meta/recipes-kernel/perf/perf_3.4.bb
>>> ...
>>> + sed -i "s:-I/usr/include/slang:-I${STAGING_INCDIR}:" ${S}/tools/perf/Makefile
>>
>> You are patching an already staged file here:
>>
>> | S = "${STAGING_KERNEL_DIR}"
>>
>> When want to fix it in this way (another workaround might be adding
>> 'WERROR=0' to EXTRA_OEMAKE), it must be done in kernel.bbclass.
That will indeed suppress the warning, but it doesn't resolve the host
contamination. A proper fix would be a patch against the kernel sources
. Every kernel will need this.
We can help you merge into the linux-yocto kernel.
>>
> Thanks, I will modify it.
>
> -Roy
>
>> Enrico
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
>>
>
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
prev parent reply other threads:[~2012-08-02 20:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 9:06 [PATCH] perf-3.4: fix hardcoded slang include dir rongqing.li
2012-07-30 9:43 ` Enrico Scholz
2012-07-31 3:24 ` Rongqing Li
2012-08-02 19:53 ` Darren Hart [this message]
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=501ADAB6.5030004@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=enrico.scholz@sigma-chemnitz.de \
--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 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.