mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Brad Hards <bhards@bigpond.net.au>
To: Russell King <rmk@arm.linux.org.uk>,
	"D. A. M. Revok" <marvin@synapse.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Compile Bogons in 2.4.19-rc3 with Caldera OpenLinux 3.1's patched 2.95.2
Date: Thu, 25 Jul 2002 14:32:52 +1000	[thread overview]
Message-ID: <200207251432.52687.bhards@bigpond.net.au> (raw)
In-Reply-To: <20020724101620.A25115@flint.arm.linux.org.uk>

On Wed, 24 Jul 2002 19:16, Russell King wrote:
> On Wed, Jul 24, 2002 at 05:03:52AM -0400, D. A. M. Revok wrote:
> > Oh, fucking great, /usr/include/asm /isn't/ a symlink to
> > /usr/src/linux/include/asm, it's its own directory.
>
> That's 100% correct.  /usr/include/asm and /usr/include/linux are supposed
> to be the kernel headers glibc was compiled with, not the kernel headers
> for the kernel you're trying to build.
I don't think that this is the whole story.

Some applications talk to the kernel (eg via ioctl()). This is related to the 
kernel version that is running (not anything to do with the libs).

In reality, we need three sets of headers:
1. Things that are kernel independent, and depend on the glibc functionality
This is probably /usr/include
2. Things that are related to the kernel that the libs are compiled against
This is probably /usr/include/sys
3. Things that are related to the kernel that is running.
This is probably /usr/include/linux

The hard part is that the applications need to be matched to the kernel
binary API, which is essentially an impossible problem unless you have
a source tree that you recompile whenever you change the kernel 
API (and an API versioning system that tells you which version you 
need for each application).

Brad
-- 
http://conf.linux.org.au. 22-25Jan2003. Perth, Australia. Birds in Black.

  parent reply	other threads:[~2002-07-25  7:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-24  8:29 D.A.M. Revok
     [not found] ` <20020724084749.GC15043@dreams.soze.net>
2002-07-24  9:03   ` D.A.M. Revok
2002-07-24  9:16     ` Russell King
2002-07-24  9:23       ` D.A.M. Revok
     [not found]       ` <E17XIMe-0001kA-00@caramon.arm.linux.org.uk>
2002-07-24  9:26         ` Russell King
2002-07-25  4:32       ` Brad Hards [this message]
2002-07-25  7:57         ` Russell King
2002-07-25  8:23           ` kernel ABI [was something about Compile Bogons...] Brad Hards
2002-07-24  9:31 ` Compile Bogons in 2.4.19-rc3 with Caldera OpenLinux 3.1's patched 2.95.2 Alex Riesen

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=200207251432.52687.bhards@bigpond.net.au \
    --to=bhards@bigpond.net.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marvin@synapse.net \
    --cc=rmk@arm.linux.org.uk \
    /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®