From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] linux-yocto-3.4: Disable extra slang header search path
Date: Tue, 7 Aug 2012 09:59:23 -0400 [thread overview]
Message-ID: <50211F3B.6010601@windriver.com> (raw)
In-Reply-To: <1344347435.9756.251.camel@ted>
On 12-08-07 09:50 AM, Richard Purdie wrote:
> On Tue, 2012-08-07 at 09:24 -0400, Bruce Ashfield wrote:
>> On 12-08-07 07:17 AM, Richard Purdie wrote:
>>> Add in a workaround to avoid host infection detection build failures
>>> from the slang include directory in perf. I'll defer to Bruce to
>>> fix this properly but we need a workaround now as this is breaking
>>> builds.
>>
>> I just followed up on a patch from 3 days ago, but I'll follow up here
>> as well .. just to make sure the message gets through.
>>
>> We had a pending patch to fix this issue from Liang Li here @ windriver.
>>
>> Did that patch not fix the problem, or did it fall through the cracks ?
>
> It is not correct. It adds in another search path and just hides the
> issue. We should *never* be putting -I/usr/include/slang on the compiler
> commandline at all period.
I'd argue that it's more correct than commenting out the upstream
include path.
It fixes the problem, doesn't require a patch to the kernel and give
us time to work upstream and get a real fix.
So I'd really prefer that we take that fix, versus the kernel patch
if it actually fixes the problem.
>
> I'd assumed in all the email traffic that this was clear and that
> another solution was being worked on that would be acceptable upstream
> too.
Exactly what I referred to above. But we don't want a temporary
kernel path, we want the temporary recipe patch.
>
> Perhaps a better option might be: -I=/usr/include/slang ? That assumes
> that all kernel gcc versions would accept the = notation, that should be
> true by now?
Not in my experience when dealing with the upstream kernel and tools,
there are plenty of old compilers floating around.
Cheers,
Bruce
>
> Cheers,
>
> Richard
>
>
>
>
next prev parent reply other threads:[~2012-08-07 14:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 11:17 [PATCH] linux-yocto-3.4: Disable extra slang header search path Richard Purdie
2012-08-07 12:53 ` Bruce Ashfield
2012-08-07 13:24 ` Bruce Ashfield
2012-08-07 13:50 ` Richard Purdie
2012-08-07 13:59 ` Bruce Ashfield [this message]
2012-08-08 2:16 ` McClintock Matthew-B29882
2012-08-08 2:18 ` Bruce Ashfield
2012-08-08 2:22 ` Bruce Ashfield
2012-08-08 2:25 ` McClintock Matthew-B29882
2012-08-08 2:30 ` Bruce Ashfield
2012-08-09 19:17 ` McClintock Matthew-B29882
2012-08-09 19:38 ` Bruce Ashfield
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=50211F3B.6010601@windriver.com \
--to=bruce.ashfield@windriver.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