From: Andreas Schwab <schwab@suse.de>
To: linux-ia64@vger.kernel.org
Subject: Re: cross-compiling ia64 kernels?
Date: Wed, 01 Nov 2006 15:38:05 +0000 [thread overview]
Message-ID: <jeac3bch42.fsf@sykes.suse.de> (raw)
In-Reply-To: <617E1C2C70743745A92448908E030B2AB91DF8@scsmsx411.amr.corp.intel.com>
Christoph Lameter <clameter@sgi.com> writes:
> + make ARCH=ia64 oldconfig
> HOSTCC scripts/basic/fixdep
> HOSTCC scripts/basic/split-include
> HOSTCC scripts/basic/docproc
> SHIPPED scripts/kconfig/zconf.tab.h
> HOSTCC scripts/kconfig/conf.o
> HOSTCC scripts/kconfig/mconf.o
> scripts/kconfig/mconf.c:91: error: static declaration of 'current_menu'
> follows non-static declaration
> scripts/kconfig/lkc.h:63: error: previous declaration of 'current_menu'
> was here
> make[1]: *** [scripts/kconfig/mconf.o] Error 1
> make: *** [oldconfig] Error 2
Your kernel sources are way out of date, this has been fixed more than two
years ago.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2006-11-01 15:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 21:20 cross-compiling ia64 kernels? Luck, Tony
2006-10-30 22:25 ` Bob Picco
2006-10-30 22:30 ` Ian Wienand
2006-10-31 7:12 ` Len Brown
2006-10-31 12:15 ` Bob Picco
2006-11-01 4:02 ` Len Brown
2006-11-01 13:33 ` Andreas Schwab
2006-11-01 15:26 ` Christoph Lameter
2006-11-01 15:38 ` Andreas Schwab [this message]
2006-11-01 17:06 ` Christoph Lameter
2006-11-01 17:43 ` Andreas Schwab
2006-11-01 17:45 ` Christoph Lameter
2006-11-01 19:15 ` Andreas Schwab
2006-11-01 19:35 ` Christoph Lameter
2006-11-01 19:46 ` Christoph Lameter
2006-11-01 22:24 ` Andreas Schwab
2006-11-01 23:30 ` Christoph Lameter
2006-11-02 0:36 ` Andreas Schwab
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=jeac3bch42.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=linux-ia64@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.