![]() | |||||||||||||
Messages in this thread |
On Thursday 27 April 2006 06:31, Linus Torvalds wrote: > > On Thu, 27 Apr 2006, David Woodhouse wrote: > > > > Agreed. And distributions and library maintainers _will_ fix them. Are > > we to deny those people the tools which will help them to keep track of > > our breakage and submit patches to fix it? > > No. As mentioned, as long as the target audience is distributions and > library maintainers, I definitely think we should do help them as much as > possible. Our problems have historically been "random people" who have > /usr/include/linux being the symlink to "kernel source of the day", which > is an unsupportable situation. Maybe we should have a script which processes kernel's include/linux/* files and produces sanitized set of headers (by deleting "#ifdef __KERNEL__" blocks, etc), which will be treated at *the* official kernel<->userspace API and will be used by glibc etc? Such "kernel header sanitizator" script is to be maintained and distributed as part of kernel tree. glibc people will then know where to look/what part of kernel to patch if they will stumble on incorrect sanitized header. I.e., they will need to either fix original kernel header so that translation of it becomes ok (for example, a missing #ifdef __KERNEL) or by modifying sanitizator script. -- vda - 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/ | ||||||||||||
| Last update: 2006-04-27 07:14 [from the cache] ©2003-2008 | |||||||||||||