From: Arjan van de Ven <arjan@infradead.org>
To: DervishD <lkml@dervishd.net>
Cc: Michal Feix <michal@feix.cz>, linux-kernel@vger.kernel.org
Subject: Re: Conflicts in kernel 2.6 headers and {glibc,Xorg}
Date: Sun, 09 Jan 2005 13:31:32 +0100 [thread overview]
Message-ID: <1105273893.4173.12.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20050109122557.GA221@DervishD>
On Sun, 2005-01-09 at 13:25 +0100, DervishD wrote:
> Hi All :)
>
> * Tomasz Torcz <zdzichu@irc.pl> dixit:
> > Mainstream distributions use ,,sanitized'' version o kernel
> > headers - Fedora has own set, Debian has another, LFS too. For rest
> > and for us, casual users, there are headers made as byproduct of
> > PLD Linux, which are used since december 2003 (before kernel 2.6
> > was even released).
>
> But the set of sanitized kernel headers, if you build your own
> software and you're not using a distro, is only available for 2.6.x
> kernels, not for 2.4.x kernels.
The headers RH ships work for both...
>
> What should be done for 2.4 kernels?
> I currently use a set of headers from the 2.4 kernel I used to build
> my libc, not the headers from the current kernel I'm running, but I
> would like to know anyway.
.... and you can use 2.6 headers to build a glibc that works excellent
for 2.4 kernels too. The kernel API/ABI *does not change on this level*
between kernel versions. Things may get added, but they do not change.
next prev parent reply other threads:[~2005-01-09 12:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-09 9:20 Conflicts in kernel 2.6 headers and {glibc,Xorg} Michal Feix
2005-01-09 11:06 ` Chris Lingard
2005-01-09 11:08 ` Tomasz Torcz
2005-01-09 11:35 ` Michal Feix
2005-01-09 11:55 ` Tomasz Torcz
2005-01-09 12:25 ` DervishD
2005-01-09 12:31 ` Arjan van de Ven [this message]
2005-01-09 15:02 ` DervishD
2005-01-09 12:59 ` Jesper Juhl
2005-01-09 16:06 ` George Georgalis
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=1105273893.4173.12.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@dervishd.net \
--cc=michal@feix.cz \
/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;
as well as URLs for NNTP newsgroup(s).