> You could argue that this is a glibc bug.
I do indeed. I further argue that it has no business being discussed on the
kernel mailing list, just because the kernel happens to have a header with
a similar name.
> But the way that glibc generates the include/linux headers is just
> to copy them from some kernel tree or other, with a little mangling
> on the side.
This errant behaviour would appear to be the cause of the bug you've
observed. Glibc should be providing its own header files.
-- dwmw2
- 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/