From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: make xconfig fails for older kernels
Date: Mon, 03 Oct 2005 21:48:56 -0600 [thread overview]
Message-ID: <4341FBA8.3020208@shaw.ca> (raw)
In-Reply-To: <4TJDn-2mm-3@gated-at.bofh.it>
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.
What gcc version? The configuration program may have had some compile
bugs with newer compilers that were fixed in later kernels. In
particular I think gcc4 is stricter about those "static declaration
follows non-static" problems.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2005-10-04 3:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4TJDn-2mm-3@gated-at.bofh.it>
2005-10-04 3:48 ` Robert Hancock [this message]
2005-10-04 9:34 ` make xconfig fails for older kernels Felix Oxley
2005-10-04 14:04 ` Felix Oxley
2005-10-04 14:12 ` Felix Oxley
2005-10-04 16:29 ` Adrian Bunk
2005-10-04 1:13 Felix Oxley
2005-10-04 2:27 ` Randy.Dunlap
2005-10-04 2:50 ` Dan C Marinescu
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=4341FBA8.3020208@shaw.ca \
--to=hancockr@shaw.ca \
--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.