All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: linux vs. linux-libc-headers?
Date: Mon, 10 May 2010 11:15:44 +0200	[thread overview]
Message-ID: <4BE7CEC0.1090300@dresearch.de> (raw)
In-Reply-To: <1273053926.18119.331.camel@mill.internal.reciva.com>

Am 05.05.2010 12:05, Phil Blundell wrote:
>>> I thought glibc was supposed to gracefully fall back on missing syscalls?
>>
>> May be, but not satisfactorily.
>>
>> E.g. we've seen that g_file_monitor (from glib) falls back to
>> polling each second instead of using inotify_init.
> 
> That sounds like it's just a bug in glibc.  I guess you should fix it
> there.

That's all very unsatisfyingly.

I had a small look into the glibc sources. I could find the
declarations for inotfiy_init1 and epoll_create1, but i could not
find any fallback code if they do not exist in the running kernel.

I also could not find something about such fallback code at all.
FAQ 3.21 describes the problem what we have but for very old
kernel versions (2.0 vs. 2.1/2.2) and it says nothing about
glibc internal fallback handling but:

"Your program should check at runtime whether the function works,
and implement a fallback."

So where did this assumption come from?

Do you have examples for such fallbacks inside glibc?

Regards,
Steffen




  parent reply	other threads:[~2010-05-10  9:19 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 [this message]
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
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=4BE7CEC0.1090300@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 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.