From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: linux-libc-headers version (reloaded)
Date: Tue, 15 Feb 2011 07:37:32 -0700 [thread overview]
Message-ID: <4D5A8FAC.5020001@mentor.com> (raw)
In-Reply-To: <4D5A89CD.803@opendreambox.org>
On 02/15/2011 07:12 AM, Andreas Oberritter wrote:
> 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?
Right. But other things can start to rely on the kernel interfaces
(where it's allowed to) as well, and often don't do the various hoops to
be forwards compatible at run time.
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-02-15 14:38 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 [this message]
2011-02-15 14:50 ` Steffen Sledz
2011-02-18 9:55 ` Steffen Sledz
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=4D5A8FAC.5020001@mentor.com \
--to=tom_rini@mentor.com \
--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 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.