Alan Cox wrote:
> > Just putting it asm-*/types.h should just about be enough.
> That is one of the headers glibc wants to import however. It wants to be
> hard for applications to do something stupid but easy for glibc to extract
> the relevant data that it actually needs (because glibc needs the kernel to
> user information to make syscalls even if it doesnt expose them to apps)
Thinking -long term- here, I wonder what a good solution for glibc would
be? Userspace including glibc should never include kernel headers but I
100% agree we should make it as easy as possible for glibc (and other
libc's) to stay in sync with the kernel<->userspace API.
I am betting glibc does not require as much work to become independent
of kernel headers... it is more work to get all the userspace apps that
reference ioctl structures and constants not using kernel headers.
-- Jeff Garzik | Only so many songs can be sung Building 1024 | with two lips, two lungs, and one tongue. MandrakeSoft | - nomeansno - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Jan 07 2002 - 21:00:26 EST