From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Felix Oxley <lkml@oxley.org>
Cc: zippel@linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: make xconfig fails for older kernels
Date: Mon, 3 Oct 2005 19:27:28 -0700 [thread overview]
Message-ID: <20051003192728.5f0c11c7.rdunlap@xenotime.net> (raw)
In-Reply-To: <200510040213.05361.lkml@oxley.org>
On Tue, 4 Oct 2005 02:13:03 +0100 Felix Oxley wrote:
>
> I have downloaded 2.6.0 + patches up to 2.6.13 from kernel.org.
>
> When I try to configure the kernel using 'make xconfig' I get the following
> error:
>
> 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: *** [xconfig] Error 2
>
> I attempted make menuconfig, make config, and make oldconfig but each failed
> with the same error,
>
> This happens on 2.6.0, 2.6.1, 2.6.2 2.6.3, 2.6.4.
> I have previously built newer kernels such as 2.6.13-rc2-rt7 without a
> problem.
>
> I was able to overcome the error by commenting out the declaration of
> current_menu in mconf.c. But I am concerned as to the cause of this problem.
>
> Does anyone have an explanation?
Sorry, not really, other than to say that make menuconfig and
make xconfig work fine for me on 2.6.4.
I just downloaded the 2.6.4 tarball and tested/verified them.
---
~Randy
You can't do anything without having to do something else first.
-- Belefant's Law
next prev parent reply other threads:[~2005-10-04 2:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 1:13 Felix Oxley
2005-10-04 2:27 ` Randy.Dunlap [this message]
2005-10-04 2:50 ` Dan C Marinescu
[not found] <4TJDn-2mm-3@gated-at.bofh.it>
2005-10-04 3:48 ` Robert Hancock
2005-10-04 9:34 ` Felix Oxley
2005-10-04 14:04 ` Felix Oxley
2005-10-04 14:12 ` Felix Oxley
2005-10-04 16:29 ` 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=20051003192728.5f0c11c7.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@oxley.org \
--cc=zippel@linux-m68k.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
all inboxes | Powered by JetHome®