On Tue, Oct 27, 2015 at 12:16:16AM +0000, Joseph Myers wrote: > On Mon, 26 Oct 2015, Rich Felker wrote: > > > On Mon, Oct 26, 2015 at 11:42:37PM +0000, Joseph Myers wrote: > > > On Mon, 26 Oct 2015, Rich Felker wrote: > > > > > > > musl explicitly does not support using a mix of libc headers and > > > > compiler-provided freestanding headers. While there may be > > > > > > In that case the GCC ports for musl should define USER_H = > > > $(EXTRA_HEADERS) like t-openbsd does. (Of course that won't work for > > > multilib builds supporting different C libraries with different > > > multilibs.) > > > > This sounds interesting. Are there practical ways it's a better > > solution than what linux.h is doing now for musl? Inability to support > > Well, it ensures the installed compiler can't find the freestanding > headers at all, because they're not installed (other than > architecture-specific intrinsics headers).
Oh. I think that breaks Linux kernel builds, which use -nostdinc then add back the gcc include directory or something like that. I don't remember the details. Rich
