Re: [musl] Re: [PATCH resent] uapi libc compat: allow non-glibc to opt out of uapi definitions

From	Florian Weimer <fweimer@redhat.com>
Newsgroups	linux.kernel
Subject	Re: [musl] Re: [PATCH resent] uapi libc compat: allow non-glibc to opt out of uapi definitions
Date	2017-06-02 09:10 +0200
Message-ID	<tNOSC-698-15@gated-at.bofh.it> (permalink)
References	<sCiYi-4ee-21@gated-at.bofh.it> <tiJYS-7cO-19@gated-at.bofh.it> <tiMWJ-Kk-17@gated-at.bofh.it> <tA2sp-17M-9@gated-at.bofh.it> <tA7Ls-4EF-25@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On 04/25/2017 02:29 PM, Carlos O'Donell wrote:
> In glibc right now we support including linux or glibc header files first,
> and this has always been a requirement from the start. This requirement dictates
> that the kernel know which libc it's being used with so it can tailor coordination.

“right now we support” is not a support commitment, but more of an
aspiration, right?

A lot of combinations are broken, especially when kernel headers are
included first.  Maybe it's time for us to admit defeat and come up with
a simpler scheme which actually works.

Thanks,
Florian

Back to linux.kernel | Previous | Next | Find similar | Unroll thread

Thread

Re: [musl] Re: [PATCH resent] uapi libc compat: allow non-glibc to  opt out of uapi definitions Florian Weimer <fweimer@redhat.com> - 2017-06-02 09:10 +0200

csiph-web