Messages in this thread | | | Date | Thu, 13 Jan 2005 11:14:08 -0500 | From | Rahul Karnik <> | Subject | Re: [ANNOUNCE] linux-libc-headers 2.6.10.0 |
| |
On Thu, 13 Jan 2005 06:51:54 -0500, Jakub Jelinek <jakub@redhat.com> wrote: > On Thu, Jan 13, 2005 at 06:46:32AM -0500, Rahul Karnik wrote: > > We are not talking about an application, but rather out of tree kernel > > modules (or rather, different versions of modules already in the > > tree). > > For kernel modules you should never use /usr/include headers though. > /lib/modules/`uname -r`/build/include headers should be used for them > instead.
I was replying to the following:
> On Thursday 13 January 2005 09:42, Mariusz Mazur wrote: > > I'm a distribution vendor. If x11 really required having current kernel > > config at compile time to function properly, I'd start sending threats to > > its authors.
"current kernel config" is the the same as /lib/modules/`uname -r`/build/include, isn't it? I was saying that kernel modules absolutely require the headers for the running kernel, just as you are. Granted, the drm makefiles may be broken anyway and point to /usr/include/linux.
Thanks, Rahul - 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/
| |