Subject: Re: 2.6.0-t1-ac2: unable to compile glibc 2.3.2
From: Chris Meadors <twrchris@hereintown.net>
To: linux-kernel@vger.kernel.org
In-Reply-To: <1058436931.5778.2.camel@laptop.fenrus.com>
References: <20030717114548.5f5d506d.martin.zwickel@technotrend.de>
	 <1058436931.5778.2.camel@laptop.fenrus.com>
Content-Type: text/plain
Message-Id: <1058463273.30267.7.camel@clubneon.priv.hereintown.net>
Mime-Version: 1.0
Date: 17 Jul 2003 13:34:33 -0400
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 883
Lines: 22

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/