This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Continuing the UAPI split
- From: Carlos O'Donell <carlos at redhat dot com>
- To: Szabolcs Nagy <Szabolcs dot Nagy at arm dot com>, Elichai Turkel <elichai dot turkel at gmail dot com>, Florian Weimer <fweimer at redhat dot com>
- Cc: nd <nd at arm dot com>, Christian Brauner <christian dot brauner at ubuntu dot com>, "linux-api at vger dot kernel dot org" <linux-api at vger dot kernel dot org>, libc-alpha <libc-alpha at sourceware dot org>
- Date: Thu, 7 Nov 2019 13:05:19 -0500
- Subject: Re: Continuing the UAPI split
- References: <CALN7hCK0EXLXjPRPr+tuuF2-uQvkLMCFDNzGhv9HS-jrAz6Hmg@mail.gmail.com> <0B17C6F2-DC2B-4192-B4AD-BD11D6B9F2B6@ubuntu.com> <87zhh7j38y.fsf@oldenburg2.str.redhat.com> <CALN7hCJ_umFqC1L0T19CuiGiGoVwac5807NDw4LiDqSD-VJL=Q@mail.gmail.com> <facb4d0d-4e20-41f0-4c01-b210c677c24c@arm.com>
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.
There ends up being a rather tight version coupling that
happens, and that's unfortunate, but a function of cost.
Fixing this so it works in the various cases is costly.
--
Cheers,
Carlos.