From: Thomas Dodd <ted@cypress.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] use correct include dir for build tools
Date: Thu, 22 Feb 2001 17:44:42 -0600 [thread overview]
Message-ID: <3A95A46A.76C50741@cypress.com> (raw)
In-Reply-To: <20010222123940.A20319@tenchi.datarithm.net> <E14W4EP-00055G-00@the-village.bc.nu> <20010222144055.B20752@tenchi.datarithm.net> <20010222150946.D20997@thune.yy.com>
Mike Castle wrote:
> (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.)
Red Hat did that for glibc-2.1.9 and glibc-2.2 in RHL-7.0.
Hundreds have complaind about /usr/include/linux
not being a sym link to /usr/src/linux/include/linux.
The kernel headers for glibc are form a pre 2.4.0 kernel
and should probably be updated along with a new glibc
built against the new headers.
I've had no problems with it so far, been running since the
pinstripe beta release.
-Thomas
prev parent reply other threads:[~2001-02-22 23:45 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
2001-02-22 23:44 ` Thomas Dodd [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=3A95A46A.76C50741@cypress.com \
--to=ted@cypress.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox