From: Thilo Fromm <t.fromm@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Kernel Headers Quality Issue
Date: Tue, 11 May 2010 09:19:39 +0200 [thread overview]
Message-ID: <4BE9050B.6010103@dresearch.de> (raw)
In-Reply-To: <1273510550.22943.298.camel@trini-m4400>
Hello, Tom,
>> this is a somewhat cumulated response - I'd like to address some of the
>> things mentioned at different points in the discussion in one place.
>> Please forgive me should I misquote things.
>>
>> Graeme Gregory in <20100505094242.GF2444@xora-desktop.xora.org.uk>:
>>
>> [Steffen Sledz]
>> > > It seem's not to be possible to use DEFAULT_PREFERENCE_hipox in the
>> > > linux-libc-headers recipes. So what's the right way to handle this?
>> > > Something like PREFERRED_VERSION_linux-libc-headers_hipox = "2.6.24"
>> > > in angstrom-2008.1.conf?
>> >
>> [Graeme Gregory]
>> > I thought glibc was supposed to gracefully fall back on missing
>> > syscalls?
>>
>> Glibc is compiled against 2.6.31 headers, which is one of our main
>> issues here. It only ever *runs* with a 2.6.24 kernel on the target
>> system, though. So it cannot know about missing syscalls until runtime.
>
> So, I think some of the confusion here stems from confusion about (and I
> don't know the right answer off-hand) how glibc handles the
> --with-kernel=VERSION stuff.
What is "--with-kernel"? Glibc offers a compile time configuration
parameter "--enable-kernel", which enables/disables *backwards support*
library compatibility support for *legacy kernel interfaces*. E.g. if
you --enable-kernel=2.2.14, you should be able to compile ancient user
space applications which make use of obsolete kernel 2.2.14
functionality against the resulting glibc. This makes systems running
*very recent kernels* provide legacy interfaces of much older kernels
via the C library. Which is the exact opposite of our situation.
The release notes on glibc 2.2.4, which introduced this option, are
quite educating (it's Ulrich Drepper writing, so be prepared):
<http://sourceware.org/ml/libc-announce/2001/msg00000.html> (about
halfway through the page).
But maybe there is a "--with-kernel" around which does the opposite to
"--enable-kernel"?
Regards,
Thilo
--
Dipl.-Ing (FH) Thilo Fromm, MSc., Embedded Systems Developer
DResearch Digital Media Systems GmbH
Otto-Schmirgal-Str. 3, D-10319 Berlin, Germany
Amtsgericht: Berlin Charlottenburg, HRB:54412
Tel: +49 (30) 515 932 228 mailto:t.fromm@dresearch.de
Fax: +49 (30) 515 932 77 http://www.dresearch.de
next prev parent reply other threads:[~2010-05-11 7:22 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 9:36 linux vs. linux-libc-headers? Steffen Sledz
2010-05-05 9:42 ` Graeme Gregory
2010-05-05 10:00 ` Steffen Sledz
2010-05-05 10:05 ` Phil Blundell
2010-05-05 14:50 ` Steffen Sledz
2010-05-06 10:15 ` [PATCH] angstrom-2008.1: use linux-libc-headers 2.6.24 for hipox machine Steffen Sledz
2010-05-06 10:42 ` Koen Kooi
2010-05-06 10:47 ` Steffen Sledz
2010-05-07 6:59 ` Steffen Sledz
2010-05-07 7:23 ` Koen Kooi
2010-05-07 7:35 ` Steffen Sledz
2010-05-10 7:36 ` Steffen Sledz
2010-05-10 8:34 ` Koen Kooi
2010-05-10 16:46 ` Tom Rini
2010-05-06 12:03 ` Steffen Sledz
2010-05-07 9:03 ` linux vs. linux-libc-headers? Phil Blundell
2010-05-10 9:15 ` Steffen Sledz
2010-05-12 10:10 ` Phil Blundell
2010-05-10 14:53 ` Kernel Headers Quality Issue (was: linux vs. linux-libc-headers?) Thilo Fromm
2010-05-10 16:55 ` Tom Rini
2010-05-10 19:00 ` Khem Raj
2010-05-14 9:25 ` Kernel Headers Quality Issue Thilo Fromm
2010-05-14 13:05 ` Phil Blundell
2010-05-11 7:19 ` Thilo Fromm [this message]
2010-05-10 19:14 ` Kernel Headers Quality Issue (was: linux vs. linux-libc-headers?) Tom Rini
2010-05-11 7:42 ` Kernel Headers Quality Issue Steffen Sledz
2010-05-11 14:27 ` Tom Rini
2010-05-12 6:02 ` Steffen Sledz
2010-05-12 15:23 ` Tom Rini
2010-05-12 16:53 ` Mark Brown
2010-05-13 11:40 ` Phil Blundell
2010-05-14 9:59 ` Thilo Fromm
2010-05-14 10:25 ` Phil Blundell
2010-05-14 11:40 ` Thilo Fromm
2010-05-14 12:38 ` Phil Blundell
2010-05-18 0:14 ` Mark Brown
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=4BE9050B.6010103@dresearch.de \
--to=t.fromm@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