From: xxxx <toxicitycom@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: make dep -problem
Date: Tue, 28 Feb 2006 04:09:11 +0000 [thread overview]
Message-ID: <1141099751.29028.1.camel@localhost.localdomain> (raw)
*** Check the top-level Makefile for additional configuration.
*** Next, you must run 'make dep'.
make[1]: Entering directory `/home/matt/uClinux-workspace/uClinux-dist'
make ARCH=m68knommu CROSS_COMPILE=m68k-elf- -C linux-2.4.x menuconfig
make[2]: Entering directory `/home/matt/uClinux-workspace/uClinux-2.4.x'
rm -f include/asm
( cd include ; ln -sf asm-m68knommu asm)
make -C scripts/lxdialog all
make[3]: Entering directory
`/home/matt/uClinux-workspace/uClinux-2.4.x/scripts/lxdialog'
make[3]: Leaving directory
`/home/matt/uClinux-workspace/uClinux-2.4.x/scripts/lxdialog'
/bin/sh scripts/Menuconfig arch/m68knommu/config.in
Using defaults found in .config
Preparing scripts: functions, parsing../MCmenu0: line 106: unexpected
EOF while looking for matching `''
./MCmenu0: line 110: syntax error: unexpected end of file
......................................................................done.
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: 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[2]: *** [menuconfig] Error 1
make[2]: Leaving directory `/home/matt/uClinux-workspace/uClinux-2.4.x'
make[1]: *** [linux_menuconfig] Error 2
make[1]: Leaving directory `/home/matt/uClinux-workspace/uClinux-dist'
make: *** [menuconfig] Error 2
[matt@localhost uClinux-dist]$
next reply other threads:[~2006-02-28 4:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-28 4:09 xxxx [this message]
2006-02-28 19:22 ` Sam Ravnborg
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=1141099751.29028.1.camel@localhost.localdomain \
--to=toxicitycom@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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