From: Tom Rini <trini@kernel.crashing.org>
To: Dan Malek <dan@mvista.com>
Cc: Brian Ford <ford@vss.fsi.com>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: menuconfig for PPC860T
Date: Tue, 9 Jan 2001 20:48:01 -0700 [thread overview]
Message-ID: <20010109204801.A28095@opus.bloom.county> (raw)
In-Reply-To: <3A5B5604.36EF3E2E@mvista.com>; from dan@mvista.com on Tue, Jan 09, 2001 at 01:18:44PM -0500
On Tue, Jan 09, 2001 at 01:18:44PM -0500, Dan Malek wrote:
> Brian Ford wrote:
>
> > For about the last week, make xconfig has stopped working for the
> > EST8260 board in the 2.5 bk tree. It dies with:
> >
> > make[1]: Entering directory `/home/ford/linux/src/linuxppc_2_5/scripts'
> > cat header.tk >> ./kconfig.tk
> > ./tkparse < ../arch/ppc/config.in >> kconfig.tk
> > statement not in menu
> > make[1]: *** [kconfig.tk] Error 1
>
> Aside from this, I don't think anything but the manual 'make config' has
> ever worked for the 8260. The problem is I set two processor type
> configuration variables, CONFIG_6xx and CONFIG_8260. Most of the
> scripts try to be "smart" and only allow one to be set. I know
> 'make menuconfig' doesn't work properly, I suspect 'make xconfig'
> does the same (unless Tom has fixed this recently :-).
I actually fixed menuconfig recently, in the 2_5 bk tree. I'll try xconfig
tomorrow and attempt to fix it.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-10 3:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 0:21 menuconfig for PPC860T Zheng, Haifei
2001-01-09 0:45 ` Dan Malek
2001-01-09 15:24 ` Tom Rini
2001-01-09 16:23 ` Brian Ford
2001-01-09 18:18 ` Dan Malek
2001-01-10 3:48 ` Tom Rini [this message]
2001-01-10 21:28 ` Tom Rini
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=20010109204801.A28095@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=dan@mvista.com \
--cc=ford@vss.fsi.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).