From: Carlos O'Donell <carlos@redhat.com>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: Szabolcs Nagy <Szabolcs.Nagy@arm.com>,
Elichai Turkel <elichai.turkel@gmail.com>, nd <nd@arm.com>,
Christian Brauner <christian.brauner@ubuntu.com>,
"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
libc-alpha <libc-alpha@sourceware.org>
Subject: Re: Continuing the UAPI split
Date: Thu, 7 Nov 2019 17:32:01 -0500 [thread overview]
Message-ID: <70a264b5-427f-fa6e-7f70-768724202d14@redhat.com> (raw)
In-Reply-To: <875zjvo2be.fsf@mid.deneb.enyo.de>
On 11/7/19 3:32 PM, Florian Weimer wrote:
> * Carlos O'Donell:
>
>> On 11/7/19 11:21 AM, Szabolcs Nagy wrote:
>>>> Or just giving up and telling users they can't just directly include
>>>> both libc headers and kernel headers?
>>>
>>> including both libc and linux headers is fragile and
>>> will break differently across the different linux
>>> libc implementations.
>>
>> We saw this all the time working in embedded.
>
> Do you mean you saw problems while you working in the embedded space?
Yes, embedded Linux to be specific.
There is a strong coupling between the kernel version and the toolchain
version, specifically because the strategies we take to solve these
problems end up being brittle in this regard.
Too new a kernel and you get new header problems not solved by your
old libc. Too new a libc and the kernel doesn't have the header
coordination fixes required for the newer software that needed the
newer libc.
Does that clarify my point?
--
Cheers,
Carlos.
next prev parent reply other threads:[~2019-11-07 22:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALN7hCK0EXLXjPRPr+tuuF2-uQvkLMCFDNzGhv9HS-jrAz6Hmg@mail.gmail.com>
2019-11-07 12:05 ` Continuing the UAPI split Christian Brauner
2019-11-07 12:10 ` Florian Weimer
2019-11-07 13:03 ` Elichai Turkel
2019-11-07 13:23 ` Florian Weimer
2019-11-07 13:36 ` Christian Brauner
2019-11-07 13:47 ` Florian Weimer
2019-11-07 14:05 ` Christian Brauner
2019-11-07 18:02 ` Carlos O'Donell
2019-11-07 16:21 ` Szabolcs Nagy
2019-11-07 18:05 ` Carlos O'Donell
2019-11-07 20:32 ` Florian Weimer
2019-11-07 22:32 ` Carlos O'Donell [this message]
2019-11-08 7:28 ` Florian Weimer
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=70a264b5-427f-fa6e-7f70-768724202d14@redhat.com \
--to=carlos@redhat.com \
--cc=Szabolcs.Nagy@arm.com \
--cc=christian.brauner@ubuntu.com \
--cc=elichai.turkel@gmail.com \
--cc=fw@deneb.enyo.de \
--cc=libc-alpha@sourceware.org \
--cc=linux-api@vger.kernel.org \
--cc=nd@arm.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;
as well as URLs for NNTP newsgroup(s).