From: David Christensen <davidc@connect4less.com>
To: Marc-Christian Petersen <m.c.p@wolk-project.de>
Cc: Michael Buesch <fsdeveloper@yahoo.de>,
mec@shout.net, linux-kernel@vger.kernel.org
Subject: Re: make menuconfig error
Date: 20 Jun 2003 14:36:23 -0700 [thread overview]
Message-ID: <1056144983.31828.50.camel@pluto.connect4less.com> (raw)
In-Reply-To: <200306202308.38124.m.c.p@wolk-project.de>
You are correct Marc! At least that's how I tripped it.
On Fri, 2003-06-20 at 14:08, Marc-Christian Petersen wrote:
> On Friday 20 June 2003 22:59, Michael Buesch wrote:
>
> Hi,
>
> > On Friday 20 June 2003 22:27, David Christensen wrote:
> > > 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.
> > Please do that. :)
> > > make: *** [menuconfig] Error 1
> I guess this is another^4 bugreport from a Mandrake Kernel where this occurs
> if you enter the ALSA menu.
>
> ciao, Marc
>
next prev parent reply other threads:[~2003-06-20 21:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-20 20:27 make menuconfig error David Christensen
2003-06-20 20:59 ` Michael Buesch
2003-06-20 21:08 ` Marc-Christian Petersen
2003-06-20 21:36 ` David Christensen [this message]
2003-06-20 21:42 ` Marc-Christian Petersen
2003-06-22 13:54 ` David Christensen
-- strict thread matches above, loose matches on Subject: below --
2003-03-31 19:34 Michael Buesch
2003-03-31 19:47 ` Robert P. J. Day
2003-03-31 19:58 ` Michael Buesch
2003-03-31 20:40 ` Sam Ravnborg
2001-10-02 13:51 make: *** [menuconfig] Error Sylvain Ravot
2001-10-02 15:26 ` Rasmus Bøg Hansen
2001-06-29 16:14 make menuconfig error axel
2001-04-21 3:59 Allen
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=1056144983.31828.50.camel@pluto.connect4less.com \
--to=davidc@connect4less.com \
--cc=fsdeveloper@yahoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@wolk-project.de \
--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