Messages in this thread | | | Subject | Re: Recent changes to sysctl.h breaks glibc | From | Martin Schlemmer <> | Date | 19 May 2003 12:43:44 +0200 |
| |
On Mon, 2003-05-19 at 07:38, Christoph Hellwig wrote: > On Sun, May 18, 2003 at 11:12:19PM +0200, Martin Schlemmer wrote: > > Yes, the standard answer. So what kernel headers should glibc > > be compiled against then ? > > None. But as glibc still hasn't been fixed use kernel headers from linux 2.4. >
Right, so who are going to tell the glibc guys that ?
----------------------------------------------------------------- configure: error: GNU libc requires kernel header files from Linux 2.0.10 or later to be installed before configuring. The kernel header files are found usually in /usr/include/asm and /usr/include/linux; make sure these directories use files from Linux 2.0.10 or later. This check uses <linux/version.h>, so make sure that file was built correctly when installing the kernel header files. To use kernel headers not from /usr/include/linux, use the configure option --with-headers. -----------------------------------------------------------------
I do not mind if thing break due to compatibility if needed to enhance an API, etc ... gcc does that enough.
The big problem however is that every time somebody screws up user space due to changes in kernel headers, the reply is always the same: "do not use kernel headers in user land"
Ok, lets say we stop doing that. How do anything user side find out specifics at compile time related to the kernel it should run on ? If we may not include kernel headers, what then?
Please understand, this is not me trolling, but everybody always have the same answer for issues like this, but no solutions.
Thanks,
-- Martin Schlemmer
- 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/
| |