From: Chris Lingard <chris@stockwith.co.uk>
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 11:06:16 +0000 [thread overview]
Message-ID: <200501091106.16050.chris@stockwith.co.uk> (raw)
In-Reply-To: <41E0F76D.7080805@feix.cz>
On Sunday 09 January 2005 09:20, you wrote:
> 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.
Linux from Scratch uses sanitized headers; if you want to use raw
headers, you should be able to solve your own problems.
http://www.lfs-matrix.de/lfs/view/stable/chapter05/linux-libc-headers.html
Chris Lingard
next prev parent reply other threads:[~2005-01-09 11:06 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 [this message]
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
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=200501091106.16050.chris@stockwith.co.uk \
--to=chris@stockwith.co.uk \
--cc=linux-kernel@vger.kernel.org \
--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).