From: Nick Warne <nick@linicks.net>
To: linux-kernel@vger.kernel.org, George Kasica <georgek@netwrx1.com>
Subject: Re: Problem compiling 2.6.12
Date: Wed, 22 Jun 2005 20:37:17 +0100 [thread overview]
Message-ID: <200506222037.17738.nick@linicks.net> (raw)
George Kasica wrote:
> Tried that here and got not much farther...here's the error:
>
> [root@eagle linux]# make bzImage
> CHK include/linux/version.h
> SPLIT include/linux/autoconf.h -> include/config/*
> HOSTCC scripts/mod/sumversion.o
> In file included from /usr/include/linux/errno.h:4,
That last line looks wrong... I think you may have symlinks linking to other
older kernel header stuff.
Easy way to test is untar the Linux.2.6.12 to a totally new location
(say /home/~/tmp/) and try a build with just the default config.
Nick
--
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."
next reply other threads:[~2005-06-22 19:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-22 19:37 Nick Warne [this message]
2005-06-22 21:30 ` Problem compiling 2.6.12 Adrian Bunk
2005-06-22 21:53 ` Nick Warne
2005-06-23 9:53 ` Adrian Bunk
2005-06-23 11:08 ` Nix
[not found] <Pine.LNX.4.62.0506240856460.10920@eagle.netwrx1.com>
[not found] ` <42BC1C43.3040505@blueyonder.co.uk>
[not found] ` <Pine.LNX.4.62.0506241258500.20958@eagle.netwrx1.com>
[not found] ` <42BC9FF1.1010400@blueyonder.co.uk>
[not found] ` <5nerb117olj7kahv0k8b1vss382ini6bfr@4ax.com>
2005-06-26 0:39 ` Sid Boyce
-- strict thread matches above, loose matches on Subject: below --
2005-06-23 21:26 Sid Boyce
2005-06-22 15:28 George Kasica
2005-06-22 15:59 ` Jesper Juhl
2005-06-22 16:44 ` Adrian Bunk
2005-06-22 19:15 ` George Kasica
2005-06-22 19:26 ` Jesper Juhl
2005-06-22 19:14 ` George Kasica
2005-06-22 19:45 ` Richard B. Johnson
2005-06-22 16:42 ` Adrian Bunk
2005-06-22 19:22 ` George Kasica
2005-06-22 21:33 ` Adrian Bunk
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=200506222037.17738.nick@linicks.net \
--to=nick@linicks.net \
--cc=georgek@netwrx1.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.