Kevin P. Fleming wrote:
>
> Yes, the kernel headers are currently borked for compiling userspace C
> libraries. The fix is going to take either a large effort to get a
> sanitized set of userspace kernel headers created, or someone to be
> willing to accept patches that fix the problems with the existing
> headers even though userspace is not supposed to be using them.
I did get glibc 2.3.2 compiled with gcc 3.3 against the 2.5.70 headers
with only 3 changes made to the glibc source.
The result on the other hand wasn't pretty. Most programs did run fine,
"ls" was not one of them. It would segfault. (Note to self: If glibc's
"make check" fails, don't install it.)
Your first comment is something I had wondered about for a while. A
stable set of userspace kernel headers. That would be nice. Of course
changes could be made to reflect new kernel interfaces. So they should
still be distributed with the kernel source. Then glibc could be
compiled against those updates, and the headers installed as the system
default. But it wouldn't be so forbidden for userspace to touch them.
-- Chris- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org 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 Jun 23 2003 - 22:00:27 EST