Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Cc: koen@openembedded.org
Subject: Re: linux-libc-headers version (reloaded)
Date: Fri, 18 Feb 2011 10:55:55 +0100	[thread overview]
Message-ID: <4D5E422B.3040703@dresearch.de> (raw)
In-Reply-To: <4D5A92BC.1010906@dresearch.de>

Am 15.02.2011 15:50, schrieb Steffen Sledz:
> Am 15.02.2011 15:12, schrieb Andreas Oberritter:
>> On 02/15/2011 11:41 AM, Steffen Sledz wrote:
>>> "Kernel headers are backwards compatible, but not forwards compatible.  This
>>> means that a program built against a C library using older kernel headers
>>> should run on a newer kernel (although it may not have access to new
>>> features), but a program built against newer kernel headers may not work on an
>>> older kernel."[2]
>>
>> Isn't this what the variable OLDEST_KERNEL is good for, when compiling
>> glibc?
> 
> If i'm right this goes to the --enable-kernel=VERSION configure option of glibc just to optimize the library.
> 
> "the configure option --enable-kernel=X.Y.Z allows to strip out compatibility for kernel versions before X.Y.Z."
> 
> Imho it is not legitimately to follow that glibc has compatibility code for all kernels greater or equal X.Y.Z.
> 
> Another question is the handling in other libc implementations.
> 
> And finally there are a lot of programs using userland kernel headers directly.

Ping!

If i interpret responses from Tom and Phil right they agree with me (or at least do not disagree). ;-)

But i miss reactions from the distro maintainers (especially Ångström).

Regards,
Steffen

-- 
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@DResearch.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058




  reply	other threads:[~2011-02-18  9:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-15 10:41 linux-libc-headers version (reloaded) Steffen Sledz
2011-02-15 14:12 ` Andreas Oberritter
2011-02-15 14:37   ` Tom Rini
2011-02-15 14:50   ` Steffen Sledz
2011-02-18  9:55     ` Steffen Sledz [this message]
2011-02-18 15:30       ` Khem Raj
2011-02-24 13:30         ` Steffen Sledz
2011-02-24 14:57           ` Andreas Oberritter
2011-02-25  7:40             ` Steffen Sledz
2011-02-25  7:51               ` Khem Raj
2011-02-25  8:14                 ` Steffen Sledz
2011-02-25 10:22                 ` Frans Meulenbroeks
2011-02-25 11:37                   ` Steffen Sledz
2011-02-25 12:11                 ` Andreas Oberritter
2011-02-25 17:28                   ` Khem Raj
2011-02-25 20:02                     ` Phil Blundell
2011-02-25 20:48                       ` Khem Raj
2011-02-26 12:47                     ` Andreas Oberritter
2011-02-26 17:08                       ` Khem Raj
2011-02-25 11:36               ` Andreas Oberritter
2011-02-25 21:05           ` Tom Rini
2011-02-26 16:14             ` Sledz, Steffen
2011-02-15 15:01   ` Phil Blundell

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=4D5E422B.3040703@dresearch.de \
    --to=sledz@dresearch.de \
    --cc=koen@openembedded.org \
    --cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox