From: Adrian Bunk <bunk@fs.tum.de>
To: "Constantine 'Gus' Fantanas" <fantanas@innocent.com>
Cc: mec@shout.net, linux-kernel@vger.kernel.org
Subject: Re: menuconfig crash
Date: Sun, 20 Jul 2003 19:37:13 +0200 [thread overview]
Message-ID: <20030720173713.GA26422@fs.tum.de> (raw)
In-Reply-To: <3F18C90B.305@innocent.com>
On Sat, Jul 19, 2003 at 12:28:59AM -0400, Constantine 'Gus' Fantanas wrote:
> To Whom it May Concern:
>
> I experienced a menuconfig crash and I am following the notication
> instructions of the error message (pasted below). At the time of the
> crash, I was in the sound configuration section and was entering the
> ALSA configuration subsection. The kernel I was trying to configure was
> a Mandrake 2.4.21 kernel: linux-2.4.21-0.18mdk.
>
> Here is the error message:
>
> -------------BEGINNING OF PASTED MATERIAL------------------------------
>
> 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: MCmenu73: 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 sounds like a known bug in at least one version of the Mandrake
kernel sources.
It doesn't occur in plain 2.4.21, please ask Mandrake for fixed kernel
sources.
> Regards,
>
> Gus Fantanas
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
prev parent reply other threads:[~2003-07-20 17:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-19 4:28 menuconfig crash Constantine 'Gus' Fantanas
2003-07-20 17:37 ` Adrian Bunk [this message]
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=20030720173713.GA26422@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=fantanas@innocent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mec@shout.net \
/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