From: Jesper Juhl <juhl-lkml@dif.dk>
To: Michal Feix <michal@feix.cz>
Cc: linux-kernel@vger.kernel.org, Tomasz Torcz <zdzichu@irc.pl>
Subject: Re: Conflicts in kernel 2.6 headers and {glibc,Xorg}
Date: Sun, 9 Jan 2005 13:59:16 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.61.0501091356580.3000@dragon.hygekrogen.localhost> (raw)
In-Reply-To: <41E1170D.6090405@feix.cz>
On Sun, 9 Jan 2005, Michal Feix wrote:
> > > First, I'm not on kernel mailing list so please CC any replies to me.
> > > Thank you.
> > >
> > > Yesterday I was recompiling my Linux from Scratch distribution for the
> > > first time with Linux kernel 2.6.10 headers as a base for glibc. I've
> > > found, that glibc (and XOrg later on too) won't compile, as there is a
> > > conflict in certain functions or macros that glibc and Kernel headers both
> > > define.
> >
> >
> > 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?
>
I think you'll find these links informative :
http://www.kernelnewbies.org/faq/
- read the section entitled "What's going on with the kernel headers ?"
http://uwsg.iu.edu/hypermail/linux/kernel/0007.3/0587.html
- that's Linus' own explanation of the header issue.
http://groups-beta.google.com/group/linux.kernel/msg/9c467432e123860a?q=kernel+headers+user+space+group:linux.kernel&rnum=2
- a bit more from Linus
--
Jesper Juhl
next prev parent reply other threads:[~2005-01-09 12:47 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
2005-01-09 15:02 ` DervishD
2005-01-09 12:59 ` Jesper Juhl [this message]
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=Pine.LNX.4.61.0501091356580.3000@dragon.hygekrogen.localhost \
--to=juhl-lkml@dif.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=michal@feix.cz \
--cc=zdzichu@irc.pl \
/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).