From: "Justin Slootsky" <slootsky@bigfoot.com>
To: <mec@shout.net>, <linux-kernel@vger.kernel.org>
Subject: kernel-source-2.2.19 - error in menuconfig
Date: Mon, 21 May 2001 09:14:52 -0400 [thread overview]
Message-ID: <001101c0e1f8$05a4cf80$0602a8c0@chase.com> (raw)
I downloaded the .deb package for kernel-source-2.2.19.
I tried to run make menuconfig and the following happened...
> bash-2.05# make menuconfig
> rm -f include/asm
> ( cd include ; ln -sf asm-i386 asm)
> make -C scripts/lxdialog all
> make[1]: Entering directory
`/usr/src/kernel-source-2.2.19/scripts/lxdialog'
> make[1]: Leaving directory
`/usr/src/kernel-source-2.2.19/scripts/lxdialog'
> /bin/sh scripts/Menuconfig arch/i386/config.in
> Using defaults found in .config
> Preparing scripts: functions, parsingawk: cannot open "MCmenu19" for
output (Too many open files)
> Awk died with error code 2. Giving up.
> .scripts/Menuconfig: ./MCmenu0: line 34: syntax error near unexpected
token `}'
> scripts/Menuconfig: ./MCmenu0: line 34: `}'
> .....scripts/Menuconfig: ./MCmenu13: line 89: syntax error: unexpected end
of file
> .............done.
then the following error showed up, so I'm reporting it as requested.
| 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: MCmenu0: 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
Justin Slootsky
slootsky@bigfoot.com
reply other threads:[~2001-05-21 13:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='001101c0e1f8$05a4cf80$0602a8c0@chase.com' \
--to=slootsky@bigfoot.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
Powered by JetHome