From: Phil Blundell <pb@pbcl.net>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] linux-libc-headers: Add big warning about antisocial behaviour
Date: Mon, 16 Sep 2013 21:52:36 +0100 [thread overview]
Message-ID: <1379364756.4770.20.camel@x121e.pbcl.net> (raw)
In-Reply-To: <CAMKF1srExVG5j4t+LdSnD3cJNJftNmykhUCRBz9wXQrv6-qH9w@mail.gmail.com>
On Mon, 2013-09-16 at 09:24 -0700, Khem Raj wrote:
> On Sat, Sep 14, 2013 at 12:19 AM, Phil Blundell <pb@pbcl.net> wrote:
> > On Fri, 2013-09-13 at 21:24 -0700, Khem Raj wrote:
> >> There are cases where we have bsps with 2.6.3x kernels and libc
> >> compiled against 3.10 assumes syscalls
> >
> > That is a bug in glibc. It should not be doing that unless configured
> > --enable-kernel=3.10.x (and this is the whole point of the
> > --enable-kernel option). If it's assuming 3.10.x syscalls under
> > --enable-kernel=2.6.x then it is broken and should be fixed.
> >
>
> we have OLDEST_KERNEL = "2.6.16" and thats not a problem. However one
> case where it showed up was when building udev > 164 with kernels
> where accept4 call was not wired for arm e.g. since udev looked up
> definition of SOCK_CLOEXEC which it found but that 2.6.32 kernel
> really did not support it.
That sounds slightly different to the problem you were originally
describing ("libc compiled against 3.10") but I think the answer is
basically still the same: it is a bug in udev, and udev ought to be
fixed.
p.
next prev parent reply other threads:[~2013-09-16 20:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 11:18 [PATCH] linux-libc-headers: Add big warning about antisocial behaviour Richard Purdie
2013-09-14 4:24 ` Khem Raj
2013-09-14 7:19 ` Phil Blundell
2013-09-16 16:24 ` Khem Raj
2013-09-16 20:52 ` Phil Blundell [this message]
2013-09-16 21:27 ` Khem Raj
2013-09-16 10:08 ` Anders Darander
2013-09-16 10:05 ` Anders Darander
2013-09-16 12:37 ` Bruce Ashfield
2013-09-16 15:47 ` Mark Hatle
2013-09-16 16:06 ` Hans Beckérus
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=1379364756.4770.20.camel@x121e.pbcl.net \
--to=pb@pbcl.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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