From: miquels@cistron-office.nl (Miquel van Smoorenburg)
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.4.1 on RHL 6.2
Date: Sat, 10 Mar 2001 18:28:09 +0000 (UTC) [thread overview]
Message-ID: <98drnp$qq0$1@ncc1701.cistron.net> (raw)
In-Reply-To: <001401c0a970$ec3c9b00$1d9509ca@pentiumiii> <200103101754.f2AHsUL04580@mailout1-100bt.midsouth.rr.com>
In article <200103101754.f2AHsUL04580@mailout1-100bt.midsouth.rr.com>,
Stephen "M." Williams <rootusr@midsouth.rr.com> wrote:
>Make sure you have the following symlinks in your /usr/include
>directory, assuming you're on an x86 machine:
>
>asm -> /usr/src/linux/include/asm-i386/
>linux -> /usr/src/linux/include/linux/
Note! You only have to have those symlinks on broken systems such
as Redhat.
Sane systems such as Debian have a copy of the kernel header files
that the C library was compiled against in /usr/include/{linux,asm}
instead of symlinks to the kernel source. Do not play the symlink
trick on those systems.
Before this turns into a flamewar: this has been discussed 20 or
so times before, and both Linus and the glibc developers agree
that you a distribution should do the latter. The headers you use
to compile userland binaries should be the same as the C library
was compiled against.
If you need to compile a standalone module use -I/usr/src/linux/include
Mike.
--
Go not unto the Usenet for advice, for you will be told both yea and nay (and
quite a few things that just have nothing at all to do with the question).
-- seen in a .sig somewhere
next prev parent reply other threads:[~2001-03-10 18:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-10 14:46 Srinath Ravinathan
2001-03-10 17:53 ` Stephen M. Williams
2001-03-10 18:28 ` Miquel van Smoorenburg [this message]
2001-03-10 19:15 ` J Sloan
2001-03-10 19:37 ` Alan Cox
2001-03-10 19:34 ` Alan Cox
2001-03-10 20:05 ` Miquel van Smoorenburg
2001-03-10 18:44 ` Stephen M. Williams
2001-03-10 18:59 ` Mohammad A. Haque
2001-03-11 16:35 Chris Andrews
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='98drnp$qq0$1@ncc1701.cistron.net' \
--to=miquels@cistron-office.nl \
--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®