All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: richard.purdie@linuxfoundation.org
Cc: saul.wold@intel.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/3] linux-libc-headers: set default LINUXLIBCVERSION to 3.2
Date: Fri, 23 Mar 2012 14:06:03 -0400	[thread overview]
Message-ID: <CADkTA4Nn_S-gotSUi_Shbq6FKZydT8jMsQPvhxrML8CzmghwMg@mail.gmail.com> (raw)
In-Reply-To: <CADkTA4PcxbK+Z7HpLj8fWvjBasGBE18MP=m9LBuByDP8bkUJHw@mail.gmail.com>

On Fri, Mar 23, 2012 at 1:57 PM, Bruce Ashfield
<bruce.ashfield@gmail.com> wrote:
> On Fri, Mar 23, 2012 at 1:07 PM, Bruce Ashfield
> <bruce.ashfield@windriver.com> wrote:
>> Switch the default libc-headers to the 3.2 version.
>
> I spoke to soon. I seeing a problem with iptables in the builds I left running.
> I know we looked at this just recently, so it may just be a matter of undoing
> that fix.
>
> I'm looking at it now, but waned to follow up right away.

Ah yes, this is the issue that was discussed with respect to some of the intel
BSPs using headers that were newer than 3.2. We temporarily avoided it by
stepping back to the 3.1 headers.

The step back isn't a great solution, so I'm looking at fixing this
properly now.

Cheers,

Bruce

>
> Bruce
>
>>
>> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
>> ---
>>  meta/conf/distro/include/tcmode-default.inc |    2 +-
>>  1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/meta/conf/distro/include/tcmode-default.inc b/meta/conf/distro/include/tcmode-default.inc
>> index 28c25db..b481163 100644
>> --- a/meta/conf/distro/include/tcmode-default.inc
>> +++ b/meta/conf/distro/include/tcmode-default.inc
>> @@ -22,7 +22,7 @@ SDKGCCVERSION ?= "4.6%"
>>  BINUVERSION ?= "2.22"
>>  EGLIBCVERSION ?= "2.13"
>>  UCLIBCVERSION ?= "0.9.33"
>> -LINUXLIBCVERSION ?= "3.1"
>> +LINUXLIBCVERSION ?= "3.2"
>>
>>  PREFERRED_VERSION_gcc ?= "${GCCVERSION}"
>>  PREFERRED_VERSION_gcc-cross ?= "${GCCVERSION}"
>> --
>> 1.7.0.4
>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end"



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"



  reply	other threads:[~2012-03-23 18:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-23 17:07 [PATCH 0/3] linux-libc-headers: 3.2 and linux-libc-headers-yocto movement Bruce Ashfield
2012-03-23 17:07 ` [PATCH 1/3] linux-libc-headers: add 3.2 headers and remove 3.1 Bruce Ashfield
2012-03-23 17:07 ` [PATCH 2/3] linux-libc-headers: set default LINUXLIBCVERSION to 3.2 Bruce Ashfield
2012-03-23 17:57   ` Bruce Ashfield
2012-03-23 18:06     ` Bruce Ashfield [this message]
2012-03-23 17:07 ` [PATCH 3/3] linux-libc-headers-yocto: remove from oe-core Bruce Ashfield
2012-03-23 17:22 ` [PATCH 0/3] linux-libc-headers: 3.2 and linux-libc-headers-yocto movement Koen Kooi
2012-03-23 17:45   ` Bruce Ashfield
2012-03-23 18:41 ` Bruce Ashfield
2012-03-25 10:11 ` Richard Purdie

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=CADkTA4Nn_S-gotSUi_Shbq6FKZydT8jMsQPvhxrML8CzmghwMg@mail.gmail.com \
    --to=bruce.ashfield@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=saul.wold@intel.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 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.