From: Brian S Queen <bqueen@nas.nasa.gov>
To: linux-kernel@vger.kernel.org
Subject: Upgrading Headers?
Date: Mon, 11 Mar 2002 17:00:08 -0800 [thread overview]
Message-ID: <200203120100.RAA00468@marcy.nas.nasa.gov> (raw)
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.
Brian McQueen
NAS Division
NASA/Ames
next reply other threads:[~2002-03-12 1:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-12 1:00 Brian S Queen [this message]
2002-03-12 1:07 ` Robert Love
2002-03-12 1:22 ` Alan Cox
2002-03-12 10:02 ` David Woodhouse
2002-03-13 19:29 ` David Ford
2002-03-12 15:41 ` Robert Love
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=200203120100.RAA00468@marcy.nas.nasa.gov \
--to=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
all inboxes | Powered by JetHome®