From: Juan Quintela <quintela@mandrakesoft.com>
To: cj_chitwood@bellsouth.net
Cc: mec@shout.net, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Possible problem report, MDK 9.1 kernel config script
Date: Fri, 11 Apr 2003 02:46:31 +0200 [thread overview]
Message-ID: <86n0ix274o.fsf@trasno.mitica> (raw)
In-Reply-To: <20030410002147.62fa9449.cj_chitwood@bellsouth.net> (cj_chitwood@bellsouth.net's message of "Thu, 10 Apr 2003 00:21:47 -0400")
>>>>> "cj" == cj chitwood <cj_chitwood@bellsouth.net> writes:
cj> Good day.
cj> I was going through the menus for kernel configuration, and received an error. The error was received when I tried to enter "Advanced Linux Sound Architecture" submenu from the sound support menu. I was dropped to my terminal, and the following output was on my screen:
cj> ################ BEGIN QUOTE ################
cj> 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: MCmenu71: command not found
cj> Please report this to the maintainer <mex@shout.net>. You may also send a problem report to <linux-kernel@vger.kernel.org>.
cj> Please indicate the kernel version you are trying to configure and which menu you were trying to enter when this error occurred.
cj> make: *** [menuconfig] Error 1
cj> [root@ip-two linux]# _
Please, update to a cooker kernel 2.4.21-0.14 or 0.15mdk cooker
kernel. This problem is fixed.
In the future, send reports about Mandrake kernels to mandrake lists
(kernel@mandrakesoft.com or cooker@mandrakesoft.com).
Later, Juan.
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
prev parent reply other threads:[~2003-04-11 0:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-10 4:21 Possible problem report, MDK 9.1 kernel config script cj_chitwood
2003-04-11 0:46 ` Juan Quintela [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=86n0ix274o.fsf@trasno.mitica \
--to=quintela@mandrakesoft.com \
--cc=cj_chitwood@bellsouth.net \
--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;
as well as URLs for NNTP newsgroup(s).