From: Saul Wold <sgw@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: McClintock Matthew-B29882 <B29882@freescale.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] kmod-native_git.bb: fix builds for hosts with older libc
Date: Tue, 21 Aug 2012 11:41:44 -0700 [thread overview]
Message-ID: <5033D668.3070909@linux.intel.com> (raw)
In-Reply-To: <CAMKF1sqAvkE=TM3KeAdW3DjaPWpDi6=8ZAGpOgBDHR7hXDwsug@mail.gmail.com>
On 08/21/2012 11:30 AM, Khem Raj wrote:
> On Tue, Aug 21, 2012 at 11:10 AM, McClintock Matthew-B29882
> <B29882@freescale.com> wrote:
>> On Tue, Aug 21, 2012 at 1:06 PM, Khem Raj <raj.khem@gmail.com> wrote:
>>> On Tue, Aug 21, 2012 at 10:59 AM, McClintock Matthew-B29882
>>> <B29882@freescale.com> wrote:
>>>> On Tue, Aug 21, 2012 at 12:54 PM, Khem Raj <raj.khem@gmail.com> wrote:
>>>>> On Tue, Aug 21, 2012 at 9:20 AM, Matthew McClintock <msm@freescale.com> wrote:
>>>>>> +
>>>>>> +do_configure_prepend (){
>>>>>> + if ! grep O_CLOEXEC -r ${includedir_native}/bits/fcntl.h; then
>>>>>> + export CFLAGS="$CFLAGS -D O_CLOEXEC=0"
>>>>>> + fi
>>>>>> +}
>>>>>
>>>>>
>>>>> IMO It would be safer to create a patch for kmod itself where you
>>>>> define O_CLOEXEC if it
>>>>> was not defined before. The above seems a bit risky
>>>>
>>>> Why is it risky? I only wanted to do this for affected systems. There
>>>> is not an easy way to do this with a patch, unless of course I apply
>>>> the patch manually.
>>>
>>> manually gripping at the host installation and then if O_CLOEXEC might
>>> be in comments
>>
>> How about grep define.*O_CLOEXEC -r ${includedir_native}/bits/fcntl.h
>>
>>> and furthermore it if it comes from fcntl.h which is not where you are
>>> looking for
>>
>> I am grepping this file though?
>
> I would go into the specific file where its asking for O_CLOEXEC
>
> and add
>
> #ifndef O_CLOEXEC
> # define O_CLOEXEC 0
> #endif
>
> and be done with it
>
Wasn't this proposed back a month ago:
http://lists.linuxtogo.org/pipermail/openembedded-core/2012-July/026343.html
And there was discussion about that approach then? I think it was
rejected due to lack of testing.
Sau!
>>
>>> there are few variables like that where its impacting more than
>>> affected systems.
>>
>> I don't follow...
>>
>> -M
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
next prev parent reply other threads:[~2012-08-21 18:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 16:20 [PATCH v2] kmod-native_git.bb: fix builds for hosts with older libc Matthew McClintock
2012-08-21 17:54 ` Khem Raj
2012-08-21 17:59 ` McClintock Matthew-B29882
2012-08-21 18:06 ` Khem Raj
2012-08-21 18:10 ` McClintock Matthew-B29882
2012-08-21 18:30 ` Khem Raj
2012-08-21 18:41 ` Saul Wold [this message]
2012-08-21 18:46 ` McClintock Matthew-B29882
2012-08-21 18:48 ` Khem Raj
2012-08-21 19:02 ` Chris Larson
2012-08-21 19:11 ` McClintock Matthew-B29882
2012-08-21 18:47 ` McClintock Matthew-B29882
2012-08-21 19:13 ` Chris Larson
2012-08-21 19:15 ` McClintock Matthew-B29882
-- strict thread matches above, loose matches on Subject: below --
2012-08-24 18:16 Matthew McClintock
2012-08-27 15:48 ` Saul Wold
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=5033D668.3070909@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=B29882@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox