| To: | "Andreas Jaeger" <aj@suse.de> |
|---|---|
| Subject: | Re: header files state |
| From: | "Kevin D. Kissell" <kevink@mips.com> |
| Date: | Mon, 20 Mar 2000 10:30:26 +0100 |
| Cc: | "Florian Lohoff" <flo@rfc822.org>, <linux@cthulhu.engr.sgi.com> |
| Sender: | owner-linuxmips@oss.sgi.com |
>Linus has stated quite violantly that glibc should not include any
>kernel headers at all - and we're now including less and less
>headers. But this process needs time and occasionally breaks older
>glibc's.
What is Linus' rationale for his position? It's true that
having includes "reaching in" from libc imposes constraints
on kernel designers, but failure to do so is guaranteed
to induce error - as we have seen.
Kevin K.
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: header files state, Kevin D. Kissell |
|---|---|
| Next by Date: | Re: header files state, Geert Uytterhoeven |
| Previous by Thread: | Re: header files state, William J. Earl |
| Next by Thread: | Re: header files state, Geert Uytterhoeven |
| Indexes: | [Date] [Thread] [Top] [All Lists] |