That's why we have some include files belonging to the kernel, and
some include files distributed with libc. Yes, this means that we
need to have coordination between kernel developers and libc
developers. But this is always necessary! Unlike the BSD camp, we
actually decouple the two, which I think is a feature. It has in
the past led to faster development processes, IMO.
This is a good point.
I suppose the "kernel version for includes" should be considered a
local configuration issue. Much of the time, it's probably ok to use
includes from an older (stable) version of the kernel. [Except for
compiling the kernel or kernel-version-specific binaries.]
I wonder if there's any reason to not export -I$(HPATH) from the top
level kernel makefile?
-- Raul