public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrzej Krzysztofowicz <kufel!ankry@green.mif.pg.gda.pl>
To: kufel!mvista.com!george@green.mif.pg.gda.pl (george anzinger)
Cc: kufel!vger.kernel.org!linux-kernel@green.mif.pg.gda.pl
	(linux-kernel@vger.kernel.org)
Subject: Re: xconfig is broken (example ppc 8xx)
Date: Wed, 2 May 2001 22:51:24 +0200 (CEST)	[thread overview]
Message-ID: <200105022051.WAA27165@kufel.dom> (raw)
In-Reply-To: <3AF031DC.B8D793FE@mvista.com> from "george anzinger" at maj 02, 2001 09:12:12

> To show the problem do:
> 
> make xconfig ARCH=ppc
> 
> in the "Platform support" menu "Processor Type" select "8xx" then close
> the subminue with "MainMenu"
> 
> now select "Save and Exit"
> 
> This produces the following error messages:
> 
> ERROR - Attempting to write value for unconfigured variable
> (CONFIG_SCC_ENET).
> ERROR - Attempting to write value for unconfigured variable
> (CONFIG_FEC_ENET).

> I think the problem is that the "wish" script builder does not allow a
> CONFIG option to be configured in two different places, even if only one

Exactly.

> of scripts should be included.

xconfig is not an on-line parser as other interpreters.
It is a script build as effect of parsing of the whole config tree
and includes all possible options.

The problem is that xconfig is based on an assumption that an
unconfigured/disabled option variable preserves its value (as "hidden")
for future reuse. It is in generel contradiction with reusing same
option in more than ane place in the config tree.

And nobody wants to rewrite xconfig (removing the mentioned above
assumption) at the end (hopefully in 2.5) of its life ...

Andrzej

  reply	other threads:[~2001-05-02 21:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-02 16:12 xconfig is broken (example ppc 8xx) george anzinger
2001-05-02 20:51 ` Andrzej Krzysztofowicz [this message]
2001-05-03 11:11 ` xconfig is broken (example ppc 8xx) [PATCH] Andrzej Krzysztofowicz

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=200105022051.WAA27165@kufel.dom \
    --to=kufel!ankry@green.mif.pg.gda.pl \
    --cc=kufel!mvista.com!george@green.mif.pg.gda.pl \
    --cc=kufel!vger.kernel.org!linux-kernel@green.mif.pg.gda.pl \
    /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