From: Adrian Bunk <bunk@fs.tum.de>
To: Daniel Lyddy <sprocket@PATH.Berkeley.EDU>
Cc: mec@shout.net, linux-kernel@vger.kernel.org
Subject: Re: Q> scripts/Menuconfig: line 832: MCmenu78: command not found
Date: Mon, 1 Sep 2003 05:12:09 +0200 [thread overview]
Message-ID: <20030901031209.GD7038@fs.tum.de> (raw)
In-Reply-To: <200308311838.25279.sprocket@path.berkeley.edu>
On Sun, Aug 31, 2003 at 06:38:25PM -0700, Daniel Lyddy wrote:
> I got this error while trying to use menuconfig to set up Kernel 2.4.22-3mdk
> sources for compilation. I was trying to enter the "alsa" part of the
> "sound" section.
>
> Menuconfig has encountered a possible error in one of the kernel's
> configuration files and is unable to continue. Here is the error
> report:
>
> Q> scripts/Menuconfig: line 832: MCmenu78: command not found
>
> Please report this to the maintainer <mec@shout.net>. You may also
> send a problem report to <linux-kernel@vger.kernel.org>.
>
> Please indicate the kernel version you are trying to configure and
> which menu you were trying to enter when this error occurred.
>
> make: *** [menuconfig] Error 1
This is a known bug in the modifications Mandrake made to it's kernel
sources.
Most likely there's already a fixed Mandrake package available, if not
please contact Mandrake.
> Dan
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2003-09-01 3:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-01 1:38 Q> scripts/Menuconfig: line 832: MCmenu78: command not found Daniel Lyddy
2003-09-01 3:12 ` Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-17 6:00 Mitch Goes
2004-02-17 15:59 ` Sam Ravnborg
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=20030901031209.GD7038@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mec@shout.net \
--cc=sprocket@PATH.Berkeley.EDU \
/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