From: Bernardo Innocenti <bernie@develer.com>
To: Valdis.Kletnieks@vt.edu, Christoph Hellwig <hch@infradead.org>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [TRIVIAL] fix include/linux/sysctl.h for userland
Date: Sat, 19 Jul 2003 20:40:49 +0200 [thread overview]
Message-ID: <200307192040.49258.bernie@develer.com> (raw)
In-Reply-To: <200307191801.h6JI1VbF012692@turing-police.cc.vt.edu>
On Sat, 19 Jul 2003 19:52:35 +0200, Bernardo Innocenti said:
> > Include linux/compiler.h in include/linux/sysctl.h. Needed to get __user
> > defined when C library uses this header (ie: no __KERNEL__).
On Saturday 19 July 2003 20:01, Valdis.Kletnieks@vt.edu wrote:
> Umm... shouldn't this be in the glibc-kernheaders version of sysctl.h
> that ends up in /usr/include rather than the kernel version?
On Saturday 19 July 2003 19:59, Christoph Hellwig wrote:
> It shouldn't be included from userspace, and glibc needs to be fixed not
> to do so.
Two reasons:
- I'm using uClibc, not glibc. uClibc doesn't have a fixed copy
of the kernel headers. Everything builds fine with real kernel
headers from both 2.4.x and 2.6.x, except for this small glitch.
- If we fix it now, the glibc guys will have one less patch to
apply when they update their copy.
The glibc-kernelheaders package exists only because the glibc
people cannot afford to work-around every single quirk in any
version of the kernel.
And if you often build system utilities you'll find out there is
quite a lot of userland code out there with legitimate reasons
for including kernel headers. Some examples: strace, nfsutils,
psutils, quota.
--
// Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/ http://www.develer.com/
Please don't send Word attachments - http://www.gnu.org/philosophy/no-word-attachments.html
prev parent reply other threads:[~2003-07-19 18:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-19 17:52 [TRIVIAL] fix include/linux/sysctl.h for userland Bernardo Innocenti
2003-07-19 17:59 ` Christoph Hellwig
2003-07-19 18:01 ` Valdis.Kletnieks
2003-07-19 18:40 ` Bernardo Innocenti [this message]
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=200307192040.49258.bernie@develer.com \
--to=bernie@develer.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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