From: "Mohammad A. Haque" <mhaque@haque.net>
To: "Stephen M. Williams" <rootusr@midsouth.rr.com>
Cc: Miquel van Smoorenburg <miquels@cistron-office.nl>,
linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.4.1 on RHL 6.2
Date: Sat, 10 Mar 2001 13:59:05 -0500 [thread overview]
Message-ID: <3AAA7979.1F923CC6@haque.net> (raw)
In-Reply-To: <001401c0a970$ec3c9b00$1d9509ca@pentiumiii> <200103101754.f2AHsUL04580@mailout1-100bt.midsouth.rr.com> <98drnp$qq0$1@ncc1701.cistron.net> <200103101845.f2AIjuL10614@mailout1-100bt.midsouth.rr.com>
"Stephen M. Williams" wrote:
>
> Wow, I had no idea. I was following advice I received a long time ago
> from a mailing list. If I remove those symlinks how do I go about
> compiling the kernel without receiving the same errors as Srinath?
Note that he said distributions such as RedHat (pre 7.0 .. I think 7.0
does it correctly). On other distros those headers are/should be
included with the glibc devel stuff.
You could probably copy those dirs into place on the broken distros
without problems.
--
=====================================================================
Mohammad A. Haque http://www.haque.net/
mhaque@haque.net
"Alcohol and calculus don't mix. Project Lead
Don't drink and derive." --Unknown http://wm.themes.org/
batmanppc@themes.org
=====================================================================
next prev parent reply other threads:[~2001-03-10 19:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-10 14:46 Srinath Ravinathan
2001-03-10 17:53 ` Stephen M. Williams
2001-03-10 18:28 ` Miquel van Smoorenburg
2001-03-10 19:15 ` J Sloan
2001-03-10 19:37 ` Alan Cox
2001-03-10 19:34 ` Alan Cox
2001-03-10 20:05 ` Miquel van Smoorenburg
2001-03-10 18:44 ` Stephen M. Williams
2001-03-10 18:59 ` Mohammad A. Haque [this message]
2001-03-11 16:35 Chris Andrews
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=3AAA7979.1F923CC6@haque.net \
--to=mhaque@haque.net \
--cc=linux-kernel@vger.kernel.org \
--cc=miquels@cistron-office.nl \
--cc=rootusr@midsouth.rr.com \
/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®