From: "Randy.Dunlap" <rddunlap@osdl.org>
To: mk.hannah@verizon.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: Menuconfig Error
Date: Sun, 25 Jan 2004 15:48:51 -0800 [thread overview]
Message-ID: <20040125154851.15600ef8.rddunlap@osdl.org> (raw)
In-Reply-To: <40144617.7040901@verizon.net>
On Sun, 25 Jan 2004 22:41:27 +0000 Mark K Hannah <mk.hannah@verizon.net> wrote:
| Following error received while trying to get into "Advanced Linux Sound
| Arch." Crashes as soon as you select.
|
| Also getting module compile errors...I assume it is because I can't get
| into ALSA parameters to shut off usbaudio under ALSA.
|
| Using Mandrake 9.2 and kernel-source-2.4.22-10mdk
| Mark Hannah
|
|
| 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
That's caused by Mandrake's integration of ALSA in 2.4.x.
Reportedly Mandrake has fixes for it, so please check with them.
--
~Randy
next prev parent reply other threads:[~2004-01-25 23:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-25 22:41 Menuconfig Error Mark K Hannah
2004-01-25 23:48 ` Randy.Dunlap [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-15 3:15 Chris
2004-01-30 22:04 menuconfig error Eric Von York Sr.
2004-01-30 22:45 ` Sam Ravnborg
2003-10-02 22:47 Michael Zouridakis
2003-08-05 6:42 Gael Lafond
2003-08-05 7:00 ` Tomas Szepe
2003-05-05 21:00 David van Hoose
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=20040125154851.15600ef8.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mk.hannah@verizon.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).