Messages in this thread | | | Date | Wed, 1 Dec 2004 19:08:19 +0100 | From | Sam Ravnborg <> | Subject | Re: [RFC] Splitting kernel headers and deprecating __KERNEL__ |
| |
On Wed, Dec 01, 2004 at 11:52:45AM +0100, Mariusz Mazur wrote: > On ?roda 01 grudzie? 2004 06:23, Sam Ravnborg wrote: > > > Linked, copied, mount --binded, whatever. Just not under the > > > name /usr/include/user, but something more meaningfull. > > > > Whats wrong with > > /lib/modules/`uname -r`/source/include/user > > /lib/modules/`uname -r`/source/include/$arch > > Those are supposed to be userland-only headers that don't just change - they > are gradually expanded. I don't see a point in having `uname -r` in there. > > And another thing - distribution vendors will *hate* anyone, that encourages > app developers to add an include path based on which kernel is being > currently run. People, that have their headers tied to their kernels are a > *minority*. Above shows how this minority could locate headers for running kernel. It is not meant to be the general solution.
Sam - 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/
| |