Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1655941 > unrolled thread

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

Started byFlorian Weimer <fweimer@redhat.com>
First post2017-06-02 09:10 +0200
Last post2017-06-02 09:10 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  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

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

FromFlorian Weimer <fweimer@redhat.com>
Date2017-06-02 09:10 +0200
SubjectRe: [musl] Re: [PATCH resent] uapi libc compat: allow non-glibc to opt out of uapi definitions
Message-ID<tNOSC-698-15@gated-at.bofh.it>
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

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web