From: Keith Owens <kaos@ocs.com.au>
To: Jocelyn Mayer <jocelyn.mayer@netgem.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fix for include/linux/fs.h in 2.4.0 kernels
Date: Sat, 03 Feb 2001 10:25:39 +1100 [thread overview]
Message-ID: <10847.981156339@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Sat, 03 Feb 2001 00:04:16 BST." <3A7B3CF0.50327D75@netgem.com>
On Sat, 03 Feb 2001 00:04:16 +0100,
Jocelyn Mayer <jocelyn.mayer@netgem.com> wrote:
>I had some problems while compiling some applications
>with the 2.4.0 kernel.
>The problem was a conflict between string.h from the libc
>and the one from the kernel, which is included in fs.h
Rule 1. Applications must not include include kernel headers directly.
Rule 2. Any glibc that has a symlink from /usr/include/{linux,asm} to
/usr/src/linux/include/{linux,asm} is wrong.
Relying on /usr/include/{linux,asm} always pointing at the current
kernel source is broken as designed. /usr/include/{linux,asm} must be
real directories that are shipped as part of glibc, not symlinks to
some random version of the kernel. Fix /usr/include.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-02 23:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-02 23:04 Fix for include/linux/fs.h in 2.4.0 kernels Jocelyn Mayer
2001-02-02 23:25 ` Keith Owens [this message]
2001-02-03 7:42 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-02-03 2:49 Frédéric L. W. Meunier
2001-02-03 3:03 ` Brian May
2001-02-03 3:10 ` Keith Owens
2001-02-03 4:21 ` Brian May
2001-02-03 4:39 ` Brian Wellington
2001-02-03 4:41 ` Brian May
2001-02-03 8:48 ` Graham Murray
2001-02-03 8:59 ` Keith Owens
2001-02-03 10:09 ` Graham Murray
2001-02-03 11:38 ` Keith Owens
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=10847.981156339@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=jocelyn.mayer@netgem.com \
--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