From: Mike Castle <dalgoda@ix.netcom.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] use correct include dir for build tools
Date: Thu, 22 Feb 2001 15:09:46 -0800 [thread overview]
Message-ID: <20010222150946.D20997@thune.yy.com> (raw)
In-Reply-To: <20010222123940.A20319@tenchi.datarithm.net> <E14W4EP-00055G-00@the-village.bc.nu> <20010222144055.B20752@tenchi.datarithm.net>
In-Reply-To: <20010222144055.B20752@tenchi.datarithm.net>; from rread@datarithm.net on Thu, Feb 22, 2001 at 02:40:55PM -0800
On Thu, Feb 22, 2001 at 02:40:55PM -0800, Robert Read wrote:
> Ok, my bad, I forgot about cross-compiles. The problem was
> scripts/split-include.c includes errno.h, which requires linux/errno.h
> to exist, and I thought it would be better to use the current kernel's
> version, rather than the system version. I guess not.
Oh no. Definitely not.
Linus went on a tirade not too long ago about that. You can search the
kernel archives for the details and long heated threads. But it comes down
to this:
For user space compiling, the kernel include files should be those that
libc was built against.
For kernel space compiling, the kernel include files should be those that
the components will link against (static or modules).
So, theoretically, a package that has both components should take care to
do the proper includes. But that's it.
(libc does usually take care to be able to build against a later kernel
version than you're running on, and determine at run time what features may
or may not be there, so one could have a 2.4.2 kernel handy to build libc
against while still running a 2.2.18 kernel. Theoretically.)
mrc
--
Mike Castle Life is like a clock: You can work constantly
dalgoda@ix.netcom.com and be right all the time, or not work at all
www.netcom.com/~dalgoda/ and be right at least twice a day. -- mrc
We are all of us living in the shadow of Manhattan. -- Watchmen
next prev parent reply other threads:[~2001-02-22 23:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-22 20:39 [PATCH] use correct include dir for build tools Robert Read
2001-02-22 22:23 ` Matthew Kirkwood
2001-02-22 22:28 ` Alan Cox
2001-02-22 22:40 ` Robert Read
2001-02-22 23:09 ` Mike Castle [this message]
2001-02-22 23:44 ` Thomas Dodd
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=20010222150946.D20997@thune.yy.com \
--to=dalgoda@ix.netcom.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 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.