On 16 Dec 1999, Miquel van Smoorenburg wrote:
> In article <cistron.E11yiah-0003qh-00@the-village.bc.nu>,
> Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> >> glibc-devel includes references to <linux/*.h> headers not
> >> <linux-version/*.h>, and no symlinks. kernel-headers includes the
> >> symlinks but they are to /usr/src/linux.
> >
> >Thats a bug IMHO then. I will go get that link fixed.
>
> If glibc-devel has /usr/include/linux -> /usr/src/linux-2.2.5-20/include/linux
> is there any reason not to put the 2.2.5-20 kernel headers directly
> into /usr/include instead of via a symlink ?
>
> ... like Debian does? ;)
> Mike.
If this is the way the headers are heading ? Who is going to
maintain the 'which kernel headers should I be using(*)' list ?
I see an easy way of automating the process , But I sure as heck
am not going to update my headers without at least compiling the
the kernel & booting it & testing & recompile a few tools that
are dependant on them & testing & ... , Please can we find an
decent way around this dilemma ? Tia, JimL
(*) <this hour>
+----------------------------------------------------------------+
| James W. Laferriere | System Techniques | Give me VMS |
| Network Engineer | 25416 22nd So | Give me Linux |
| babydr@baby-dragons.com | DesMoines WA 98198 | only on AXP |
+----------------------------------------------------------------+
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/