mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dan C Marinescu <dan_c_marinescu@yahoo.com>
To: "Randy.Dunlap" <rdunlap@xenotime.net>, 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:50:16 -0700 (PDT)	[thread overview]
Message-ID: <20051004025016.78963.qmail@web35513.mail.mud.yahoo.com> (raw)
In-Reply-To: <20051003192728.5f0c11c7.rdunlap@xenotime.net>

make oldconfig, menuconfig, gconfig work fine with me
(_but_ using a 2.6.13.2 .config -- so the jump is
smaller...)
make xconfig gives me troubles 2 (static parser...)
another way to go would be to explicitly save your old
(2.6.4) .config into something like .config-randy...
then consume it... (xconfig will not find a .config /
implicitly work, then you fool it by loading
.config-randy) that _should_ do it... if still not
working, mrproper the old 6.4 then goto
.config-randy... my $.02


   daniel



--- "Randy.Dunlap" <rdunlap@xenotime.net> wrote:

> 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
> -
> To unsubscribe from this list: send the line
> "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at 
> http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 



		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com

  reply	other threads:[~2005-10-04  2:50 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
2005-10-04  2:50   ` Dan C Marinescu [this message]
     [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=20051004025016.78963.qmail@web35513.mail.mud.yahoo.com \
    --to=dan_c_marinescu@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@oxley.org \
    --cc=rdunlap@xenotime.net \
    --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

Powered by JetHome