From: Miles Lane <miles@megapathdsl.net>
To: Miles Lane <miles@megapathdsl.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.20 -- /usr/include/linux/errno.h:4: asm/errno.h: No such file or directory
Date: 04 Jun 2002 01:15:30 -0700 [thread overview]
Message-ID: <1023178531.7829.35.camel@agate> (raw)
In-Reply-To: <1023171718.7825.1.camel@agate>
On Mon, 2002-06-03 at 23:21, Miles Lane wrote:
> gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o split-include
> split-inIn file included from /usr/include/bits/errno.h:25,
> from /usr/include/errno.h:36,
> from split-include.c:26:
> /usr/include/linux/errno.h:4: asm/errno.h: No such file or directory
> make[1]: *** [split-include] Error 1
>
> I recall seeing a comment that egcs support was being removed.
> I am building on a machine I haven't used in a while and
> just noticed it has egcs on it. If this error is egcs-specific,
> could we please check the gcc version and emit an error stating
> that egcs isn't supported?
I figured out I needed a copy of the 2.2 kernel headers for egcs
to work. I think I made enough room to build gcc 2.95.3 (which is
listed as the gcc to use in Documentation/Changes).
Miles
prev parent reply other threads:[~2002-06-04 7:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 6:21 2.5.20 -- /usr/include/linux/errno.h:4: asm/errno.h: No such file or directory Miles Lane
2002-06-04 8:15 ` Miles Lane [this message]
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=1023178531.7829.35.camel@agate \
--to=miles@megapathdsl.net \
--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