public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: george anzinger <george@mvista.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: xconfig is broken (example ppc 8xx)
Date: Wed, 02 May 2001 09:12:12 -0700	[thread overview]
Message-ID: <3AF031DC.B8D793FE@mvista.com> (raw)

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).

The named CONFIG options are not set, nor are a few others related to
CONFIG_SCC_ENET.
(This means the on board NIC is not configured and since this is usually
a disc less system, boot fails when trying to mount "/" over nfs.)

make menueconfig ARCH=ppc  works correctly.

The problem appears to be related to these lines in
../ARCH/ppc/config.in


if [ "$CONFIG_CPU_PPC_8xx" = "y" ]; then
source arch/ppc/8xx_io/Config.in
fi

if [ "$CONFIG_CPU_PPC_8260" = "y" ]; then
source arch/ppc/8260_io/Config.in
fi

Only one of the two files is included, however, both configure the two
options mentioned in the error messages.

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
of scripts should be included.

Additional info: Kernel revs tested 2.4.2, 2.4.3
If you swap the two "if" phrases above, the 8xx config works but the
8260 fails in the same way.  I.e. the last one wins.

             reply	other threads:[~2001-05-02 16:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-02 16:12 george anzinger [this message]
2001-05-02 20:51 ` xconfig is broken (example ppc 8xx) Andrzej Krzysztofowicz
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=3AF031DC.B8D793FE@mvista.com \
    --to=george@mvista.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox