From: Robert Love <rml@tech9.net>
To: Brian S Queen <bqueen@nas.nasa.gov>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Upgrading Headers?
Date: 11 Mar 2002 20:07:05 -0500 [thread overview]
Message-ID: <1015895241.928.107.camel@phantasy> (raw)
In-Reply-To: <200203120100.RAA00468@marcy.nas.nasa.gov>
In-Reply-To: <200203120100.RAA00468@marcy.nas.nasa.gov>
On Mon, 2002-03-11 at 20:00, Brian S Queen wrote:
> When a person switches to, or upgrades a kernel, how do they upgrade the
> associated header files? The headers in /usr/include won't match the kernel.
> I don't see anything about that in the documentation.
>
> When I want to program with my new kernel I need to use the new headers, so I
> have to use #include <linux/fcntl.h> instead of #include <fcntl.h>. This
> seems odd.
You don't. The headers in /usr/include/linux and /usr/include/asm
(which may be a symlink to /usr/src/linux/include/linux and
/usr/src/linux/include/asm, respectively) should point to the kernel
headers that were present when _glibc_ was compiled.
Thus the kernel headers should match your current glibc, not your
current kernel. This is fine because the kernel will maintain backward
compatibility with the previous interfaces.
If there is something in the new kernel you want/need, recompile your
glibc against those new kernel headers and install accordingly.
Robert Love
next prev parent reply other threads:[~2002-03-12 1:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-12 1:00 Upgrading Headers? Brian S Queen
2002-03-12 1:07 ` Robert Love [this message]
2002-03-12 1:22 ` Alan Cox
2002-03-12 10:02 ` David Woodhouse
2002-03-12 15:41 ` Robert Love
2002-03-13 19:29 ` David Ford
-- strict thread matches above, loose matches on Subject: below --
2002-03-12 17:40 Brian S Queen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1015895241.928.107.camel@phantasy \
--to=rml@tech9.net \
--cc=bqueen@nas.nasa.gov \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox