Re: Conflicts in kernel 2.6 headers and {glibc,Xorg}

From: Tomasz Torcz <zdzichu@irc.pl>
To: Michal Feix <michal@feix.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Conflicts in kernel 2.6 headers and {glibc,Xorg}
Date: Sun, 9 Jan 2005 12:55:54 +0100	[thread overview]
Message-ID: <20050109115554.GA9183@irc.pl> (raw)
In-Reply-To: <41E1170D.6090405@feix.cz>

On Sun, Jan 09, 2005 at 12:35:41PM +0100, Michal Feix wrote:
> > Are you using proper kernel headers - from
> >http://ep09.pld-linux.org/~mmazur/linux-libc-headers/ ?
> 
> No, I am not, because I wasn't told to do so. For meny years I always 
> used vanilla sources from kernel.org for my /usr/include/... I wasn't 
> told, that it is wrong and I still believe, that Linux kernel headers 
> should be fixed by including these conflicting macros and functions into 
> __KERNEL__ block instead. Or am I missing something?

 According to Linus, using straight kernel headers for /usr/include
is obsolete for 10 (ten) years now. I do not agree, but kernel
developers do.
 There was few discussion on this topic. Here's one Linus post:
http://www.ussg.iu.edu/hypermail/linux/kernel/0007.3/0587.html
 Here you can find latest thread about fixing this issue:
http://lkml.org/lkml/2004/11/26/106

 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).

 Cheers,
-- 
Tomasz Torcz                Only gods can safely risk perfection,
zdzichu@irc.-nie.spam-.pl     it's a dangerous thing for a man.  -- Alia