From: David Woodhouse <dwmw2@infradead.org>
To: Robert Love <rml@tech9.net>
Cc: Brian S Queen <bqueen@nas.nasa.gov>, linux-kernel@vger.kernel.org
Subject: Re: Upgrading Headers?
Date: Tue, 12 Mar 2002 10:02:27 +0000 [thread overview]
Message-ID: <6468.1015927347@redhat.com> (raw)
In-Reply-To: <1015895241.928.107.camel@phantasy>
In-Reply-To: <1015895241.928.107.camel@phantasy> <200203120100.RAA00468@marcy.nas.nasa.gov>
rml@tech9.net said:
> You don't. The headers in /usr/include/linux and /usr/include/asm
> (which may be a symlink to /usr/src/linux/include/linux and /usr/src/
> linux/include/asm, respectively) should point to the kernel headers
> that were present when _glibc_ was compiled.
No it may not be a symlink. That would be broken.
--
dwmw2
next prev parent reply other threads:[~2002-03-12 10:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-12 1:00 Upgrading Headers? Brian S Queen
2002-03-12 1:07 ` Robert Love
2002-03-12 1:22 ` Alan Cox
2002-03-12 10:02 ` David Woodhouse [this message]
2002-03-12 15:41 ` Robert Love
2002-03-13 19:29 ` David Ford
-- strict thread matches above, loose matches on Subject: below --
2002-03-12 17:40 Brian S Queen
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=6468.1015927347@redhat.com \
--to=dwmw2@infradead.org \
--cc=bqueen@nas.nasa.gov \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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