From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: linux-libc-headers version (reloaded)
Date: Tue, 15 Feb 2011 11:41:53 +0100 [thread overview]
Message-ID: <4D5A5871.7000005@dresearch.de> (raw)
While doing some maintenance for our hipox machine i hit a problem which was discussed controversially a few months before on this ML[1] but was not solved completely in my opinion.
The basic question was if it is valid to use PREFERRED_VERSION_linux-libc-headers higher than the kernel version (like e.g angstrom-2008.1 does).
After some research on that topic i really believe this is not allowed. My strongest argument is the kernel docu itself:
"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]
Also i did not found a linux distribution providing kernel headers newer than the kernel (whilst there are some with kernel headers older than the used kernel, e.g. openSUSE 11.3 with latest updates).
So i think the way the Ångström distribution handles this is wrong. If PREFERRED_VERSION_linux-libc-headers is set to 2.6.31 no kernel older than 2.6.31 should be allowed to guarantee the full functionality of all programs!
[1] <http://thread.gmane.org/gmane.comp.handhelds.openembedded/32375>
[2] Documentation/make/headers_install.txt
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
next reply other threads:[~2011-02-15 10:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 10:41 Steffen Sledz [this message]
2011-02-15 14:12 ` linux-libc-headers version (reloaded) Andreas Oberritter
2011-02-15 14:37 ` Tom Rini
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=4D5A5871.7000005@dresearch.de \
--to=sledz@dresearch.de \
--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