All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: linux-libc-headers 2.6.37
Date: Tue, 13 Dec 2011 15:43:25 -0800	[thread overview]
Message-ID: <4EE7E31D.5040005@linux.intel.com> (raw)
In-Reply-To: <4EE7E298.5030905@windriver.com>



On 12/13/2011 03:41 PM, Bruce Ashfield wrote:
> On 11-12-13 6:33 PM, Darren Hart wrote:
>> We currently build at least some MACHINES with 2.6.37 of
>> linux-libc-headers. This can cause problems for newer packages (such as
>> connman) that expect more recent headers (if_alg.h is missing prior to
>> 2.6.39). While the proper fix is to ensure these packages can cope with
>> older headers, for MACHINES shipping 3.0+ kernels, seems to me we should
>> be using the linux-libc-headers matching the kernels. I know this has
>> come up in the past, but I don't recall if we have clearly stated and
>> justified what our policy is here.
> 
> They should match were possible. I updated master to have 3.0 and 3.1
> headers and no longer have .37 as the default.
> 
> Where is the 2.6.37 trickling in ? i.e. which boards/branch ?

This was on fri2 yocto/standard/fri2.

> 
> Bruce
> 
>>
>> Any thoughts on this?
>>
> 

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


  reply	other threads:[~2011-12-13 23:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-13 23:33 linux-libc-headers 2.6.37 Darren Hart
2011-12-13 23:41 ` Bruce Ashfield
2011-12-13 23:43   ` Darren Hart [this message]
2011-12-14  5:22     ` 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=4EE7E31D.5040005@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=bruce.ashfield@windriver.com \
    --cc=yocto@yoctoproject.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.