From: Chris Lingard <chris@ukpost.com>
To: MALET JL <malet.jean-luc@laposte.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [linux 2.6.3] [gcc 3.3.3] compile errors. Now OT
Date: Tue, 24 Feb 2004 10:46:07 +0000 [thread overview]
Message-ID: <200402241046.07323.chris@ukpost.com> (raw)
In-Reply-To: <403B0E92.60903@laposte.net>
On Tuesday 24 February 2004 8:42 am, MALET JL wrote:
> O_O! question what is the purpose of having two set of headers? do you
> think this is good work to provide a unsable set of headers with a
> software? why not include the RedHat's one then......
I think that this is off topic for this list; so I will email you direct,
quite soon, with some reasons and links.
Nothing wrong with using RedHat, nice distro; but your question was about
building with 2.6.x headers. The functionality of 2.6.x is needed by glibc;
but not in user space. How that is achieved is quite difficult.
Chris
next prev parent reply other threads:[~2004-02-24 10:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-22 20:31 [linux 2.6.3] [gcc 3.3.3] compile errors mjl
2004-02-23 15:42 ` Randy.Dunlap
2004-02-23 16:31 ` MALET JL
2004-02-23 16:58 ` Chris Lingard
2004-02-24 8:42 ` MALET JL
2004-02-24 10:46 ` Chris Lingard [this message]
2004-02-23 20:52 ` Martin Schlemmer
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=200402241046.07323.chris@ukpost.com \
--to=chris@ukpost.com \
--cc=linux-kernel@vger.kernel.org \
--cc=malet.jean-luc@laposte.net \
/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.