public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frédéric L. W. Meunier <0@pervalidus.net>
To: Keith Owens <kaos@ocs.com.au>, Jocelyn Mayer <jocelyn.mayer@netgem.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Fix for include/linux/fs.h in 2.4.0 kernels
Date: Sat, 3 Feb 2001 00:49:26 -0200	[thread overview]
Message-ID: <20010203004926.M160@pervalidus.dyndns.org> (raw)

Keith Owens wrote:

> Rule 2. Any glibc that has a symlink from
> /usr/include/{linux,asm} to /usr/src/linux/include/{linux,asm}
> is wrong.

Such symlinks are created by the user.

> Relying on /usr/include/{linux,asm} always pointing at the
> current kernel source is broken as designed.

>From glibc 2.2.1 FAQ:

2.17.   I have /usr/include/net and /usr/include/scsi as symlinks
	into my Linux source tree.  Is that wrong?

{PB} This was necessary for libc5, but is not correct when
using glibc. Including the kernel header files directly in user
programs usually does not work (see question 3.5). glibc
provides its own <net/*> and <scsi/*> header files to replace
them, and you may have to remove any symlink that you have in
place before you install glibc. However, /usr/include/asm and
/usr/include/linux should remain as they were.

Keith, are you saying that glibc is wrong?

3.5.    On Linux I've got problems with the declarations in Linux
	kernel headers.

{UD,AJ} On Linux, the use of kernel headers is reduced to the
minimum. This gives Linus the ability to change the headers
more freely. Also, user programs are now insulated from changes
in the size of kernel data structures.

For example, the sigset_t type is 32 or 64 bits wide in the
kernel. In glibc it is 1024 bits wide. This guarantees that
when the kernel gets a bigger sigset_t (for POSIX.1e realtime
support, say) user programs will not have to be recompiled.
Consult the header files for more information about the
changes.

Therefore you shouldn't include Linux kernel header files
directly if glibc has defined a replacement. Otherwise you
might get undefined results because of type conflicts.

> /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.

But make install didn't create them. I built 2.2 and 2.2.1.

-- 
Frédéric L. W. Meunier - http://www.pervalidus.net/
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR)
-
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/

             reply	other threads:[~2001-02-03  2:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-03  2:49 Frédéric L. W. Meunier [this message]
2001-02-03  3:03 ` Fix for include/linux/fs.h in 2.4.0 kernels 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
  -- strict thread matches above, loose matches on Subject: below --
2001-02-02 23:04 Jocelyn Mayer
2001-02-02 23:25 ` Keith Owens
2001-02-03  7:42   ` Alan Cox

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=20010203004926.M160@pervalidus.dyndns.org \
    --to=0@pervalidus.net \
    --cc=jocelyn.mayer@netgem.com \
    --cc=kaos@ocs.com.au \
    --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