Re: [PATCH 0/9] kbuild: uapi: remove usage of toolchain headers
Thomas Weißschuh <[email protected]> Fri, 27 Feb 2026 10:38:20 +0100
| Newsgroups | org.kernel.vger.linux-hexagon,org.kernel.vger.linux-kbuild,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <20260227103449-a526a376-153c-4f86-bfc9-2eddbdde58fd@linutronix.de> |
On Fri, Feb 27, 2026 at 10:18:41AM +0100, Arnd Bergmann wrote: > On Fri, Feb 27, 2026, at 07:37, Thomas WeiÃschuh wrote: > > Currently the test compilation of some UAPI headers requires a toolchain > > libc headers. Remove that dependency. > > > > Signed-off-by: Thomas WeiÃschuh <[email protected]> > > Nice work! > > Acked-by: Arnd Bergmann <[email protected]> > > I had toyed around with a similar series, using a slightly different > approach of always using the in-kernel nolibc headers, and making > those compile across all architectures (using empty stubs for those > that are missing syscall entry functions). > > I don't care much which way we do this as long as we can build test > the headers, but I wonder what your reason was for picking this > approach over the other. My goal is to reduce the reliance of the UAPI headers on libc ones. Hopefully we can remove libc usages from the UAPI headers and then also drop the compatibility bits from the stub headers. If we use the full nolibc the message to UAPI authors would not be clear and new dependencies may be introduced again. Thomas