From: Chris Meadors <twrchris@hereintown.net>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-t1-ac2: unable to compile glibc 2.3.2
Date: 17 Jul 2003 13:34:33 -0400 [thread overview]
Message-ID: <1058463273.30267.7.camel@clubneon.priv.hereintown.net> (raw)
In-Reply-To: <1058436931.5778.2.camel@laptop.fenrus.com>
On Thu, 2003-07-17 at 06:15, Arjan van de Ven wrote:
> you're probably better off using not-the-kernel headers for building
> glibc. eg on a RHL distro it's glibc-kernheaders package, other distros
> have different package names for these files.
In the past I would grab the headers of the kernel of which I compiled
glibc against. glibc has #ifdefs in it to turn on/off some features
based on the kernel version.
Are there plans get a sane set of kernel headers together that can be
used by userspace (at least glibc) that properly describe the features
of the current kernel, so the C library may take advantage of them?
--
Chris
next prev parent reply other threads:[~2003-07-17 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 9:45 2.6.0-t1-ac2: unable to compile glibc 2.3.2 Martin Zwickel
2003-07-17 10:15 ` Arjan van de Ven
2003-07-17 17:34 ` Chris Meadors [this message]
2003-07-17 12:12 ` 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=1058463273.30267.7.camel@clubneon.priv.hereintown.net \
--to=twrchris@hereintown.net \
--cc=linux-kernel@vger.kernel.org \
/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).