From: Christoph Hellwig <hch@infradead.org>
To: "Mark H. Wood" <mwood@IUPUI.Edu>
Cc: Linux kernel list <linux-kernel@vger.kernel.org>,
libc-alpha@sources.redhat.com
Subject: Re: One more time: /usr/include/linux, /usr/include/asm
Date: Wed, 20 Nov 2002 23:14:03 +0000 [thread overview]
Message-ID: <20021120231403.A4533@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0211201643180.359-100000@mhw.ULib.IUPUI.Edu>; from mwood@IUPUI.Edu on Wed, Nov 20, 2002 at 05:05:45PM -0500
On Wed, Nov 20, 2002 at 05:05:45PM -0500, Mark H. Wood wrote:
> No dice. glibc 2.3.1 still installs headers into /usr/include/{VARIOUS}
> which refer to /usr/include/linux and /usr/include/asm but does not supply
> that to which they refer. *sigh* After rummaging through several long
> threads in the archives, I still don't have an answer to the following:
>
> 1. What is supposed to be in /usr/include/linux and /usr/include/asm?
There is no specification on what is supposed to be there. For
compatiblity with programs written for old linux interfaces it is a good
idea to either place a copy of older kernel headers (2.2/2.4) or some
specific package to just provide those interfaces (like the redhat
glib-kernheaders rpm) there.
Note: glibc is one of the most-widely known packages that still
uses these obsolete interfaces
Note2: linux 2.5 headers slowly change to be no more compatible to those
interfaces, don't ever put copies of linux 2.5 headers there.
> 2. Where does the information come from?
It doesn't matter.
> 3. Who is responsible for putting it there?
The system integrator.
> I note that the glibc 2.3.1 instructions *still* instruct the reader to
> symlink these paths into "the 2.2 kernel sources". (See "Specific advice
> for GNU/Linux systems" in INSTALL.) I'll happily submit a glibc bug
> report, or documentation patches, or some such, just so long as someone
> can give me answers which work both for the kernel and for the library.
I've Cc'ed libc-alpha now because that's a glibc, not a kernel problem.
It's really a pity that glibc hasn't cought up _yet_.
next prev parent reply other threads:[~2002-11-20 23:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-20 22:05 Mark H. Wood
2002-11-20 23:14 ` Christoph Hellwig [this message]
2002-11-21 12:50 ` Denis Vlasenko
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=20021120231403.A4533@infradead.org \
--to=hch@infradead.org \
--cc=libc-alpha@sources.redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mwood@IUPUI.Edu \
/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
all inboxes | Powered by JetHome®