From: David Woodhouse <dwmw2@infradead.org>
To: daveanderson@eudoramail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Can't compilete 2.4.2 kernel
Date: Wed, 28 Feb 2001 14:01:26 +0000 [thread overview]
Message-ID: <7974.983368886@redhat.com> (raw)
In-Reply-To: <EOFHHHCCDNNKDAAA@shared1-mail.whowhere.com>
In-Reply-To: <EOFHHHCCDNNKDAAA@shared1-mail.whowhere.com>
daveanderson@eudoramail.com said:
> /usr/include/bits/errno.h:25: linux/errno.h: No such file or directory
Your glibc include files are broken. Rather than having their own copy of
the /usr/include/linux/ directory, they have a symlink into
/usr/src/linux/include/linux.
The correct fix is to put the kernel header files against which your glibc
was compiled into the /usr/include/linux/ directory. But it should suffice,
for now, to fix the symlink which you've broken by moving your kernel
sources.
--
dwmw2
next prev parent reply other threads:[~2001-02-28 14:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-28 13:45 Can't compilete 2.4.2 kernel David Anderson
2001-02-28 13:49 ` Mr. James W. Laferriere
2001-02-28 14:01 ` David Woodhouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-28 14:32 David Anderson
2001-03-01 0:27 ` Erik Mouw
2001-02-28 15:00 Xavier Ordoquy
2001-03-01 4:04 David Anderson
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=7974.983368886@redhat.com \
--to=dwmw2@infradead.org \
--cc=daveanderson@eudoramail.com \
--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