From: Russell King <rmk@arm.linux.org.uk>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@transmeta.com>
Subject: [PATCH] 2.5.43-menuconfig
Date: Thu, 17 Oct 2002 11:45:29 +0100 [thread overview]
Message-ID: <E18289h-0007tu-00@flint.arm.linux.org.uk> (raw)
This patch appears not to be in 2.5.43, but applies cleanly.
This patch fixes a failure case in menuconfig which can occur if a kernel
tree is configured on one architecture with menuconfig, and then attempted
to be reconfigured on another architecture.
The kernel detects that the binary can't be run on the second architecture
and correctly returns the appropriate error code. However, the Menuconfig
script ignores this error and retries endlessly, appearing to hang.
This patch makes menuconfig display a message and exit rather than
endlessly looping.
scripts/Menuconfig | 20 ++++++++++++++++++++
1 files changed, 20 insertions
diff -ur orig/scripts/Menuconfig linux/scripts/Menuconfig
--- orig/scripts/Menuconfig Sat Oct 12 10:02:17 2002
+++ linux/scripts/Menuconfig Sat Oct 12 10:45:13 2002
@@ -909,6 +909,26 @@
cleanup
exit 139
;;
+ 126|127)
+ stty sane
+ clear
+ cat << EOM
+
+There seems to be a problem with the lxdialog companion utility which is
+built prior to running Menuconfig. lxdialog could not be found, or could
+not be executed. This can be caused when lxdialog has been built for a
+different architecture.
+
+You should rebuild lxdialog. This can be done by moving to the
+/usr/src/linux/scripts/lxdialog directory and issuing the "make clean all"
+command.
+
+If the problem persists, you may email the maintainer <mec@shout.net> or
+post a message to <linux-kernel@vger.kernel.org> for additional assistance.
+
+EOM
+ cleanup
+ exit 1
esac
done
}
reply other threads:[~2002-10-17 10:41 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=E18289h-0007tu-00@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®