All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ethan Benson <erbenson@alaska.net>
To: Martin Costabel <costabel@wanadoo.fr>
Cc: "Timothy A. Seufert" <tas@mindspring.com>,
	Michael Norton <mnorton@cisco.com>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: kernel source rpm
Date: Mon, 30 Oct 2000 01:16:02 -0900	[thread overview]
Message-ID: <20001030011602.O3768@plato.local.lan> (raw)
In-Reply-To: <39FD404C.2E213ADA@wanadoo.fr>; from costabel@wanadoo.fr on Mon, Oct 30, 2000 at 10:33:00AM +0100

[-- Attachment #1: Type: text/plain, Size: 721 bytes --]

On Mon, Oct 30, 2000 at 10:33:00AM +0100, Martin Costabel wrote:

> > Don't do that.  Kernel header files are not intended to be directly
> > #include'd into user applications.  Use the the GNU C and/or C++
> > libraries and headers like you're supposed to, and you will not
> > depend on kernel files at all.
> 
> This is correct in the Linus-approved True Linux Userspace (tm). Problem
> is that on RedHat based systems like linuxppc, glibc doesn't contain
> /usr/include/linux except as a symlink to /usr/src/linux/include/linux.
> So you need either kernel sources from some archive or the
> "kernel-headers" RPM.

or Debian GNU/Linux

/me ducks

-- 
Ethan Benson
http://www.alaska.net/~erbenson/

[-- Attachment #2: Type: application/pgp-signature, Size: 0 bytes --]

      reply	other threads:[~2000-10-30 10:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-28 19:36 kernel source rpm Michael Norton
2000-10-30  9:08 ` Timothy A. Seufert
2000-10-30  9:33   ` Martin Costabel
2000-10-30 10:16     ` Ethan Benson [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=20001030011602.O3768@plato.local.lan \
    --to=erbenson@alaska.net \
    --cc=costabel@wanadoo.fr \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=mnorton@cisco.com \
    --cc=tas@mindspring.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.