From: Neo Wee Teck <weeteck@linux.net>
To: Mark Hahn <hahn@physics.mcmaster.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel include file
Date: Sun, 7 Dec 2003 08:19:29 -0800 (PST) [thread overview]
Message-ID: <20031207161929.7E0953951@sitemail.everyone.net> (raw)
Hmm... wrong idea...
<new kernel>/include/linux
update to..
/usr/include/linux
Should I?
--- Mark Hahn <hahn@physics.mcmaster.ca> wrote:
> After upgrading to a newer version of the kernel, should I also copy/update the include folder to /usr/include?
no! /usr/include is userspace, which shall never use kernel headers.
the headers you find in /usr/include that *look* like kernel headers
are in fact from glibc.
_____________________________________________________________
Linux.Net -->Open Source to everyone
Powered by Linare Corporation
http://www.linare.com/
next reply other threads:[~2003-12-07 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-07 16:19 Neo Wee Teck [this message]
2003-12-09 3:07 ` Kernel include file Matthew Reppert
-- strict thread matches above, loose matches on Subject: below --
2003-12-07 15:54 Neo Wee Teck
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=20031207161929.7E0953951@sitemail.everyone.net \
--to=weeteck@linux.net \
--cc=hahn@physics.mcmaster.ca \
--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;
as well as URLs for NNTP newsgroup(s).