From: "Dr. David Alan Gilbert" <gilbertd@treblig.org>
To: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.arm.linux.org.uk
Cc: mec@shout.net
Subject: Of hanging menuconfig [cause found]
Date: Sat, 24 Aug 2002 16:13:29 +0100 [thread overview]
Message-ID: <20020824151329.GB735@gallifrey> (raw)
Hi,
make menuconfig will hang just after the parsing in the
activate_menu loop in the case where the file scripts/lxdialog/lxdialog
won't execute. Some error codes in this case are caught; but the case
where the file scripts/lxdialog/lxdialog is a binary for the wrong
architecture (case 126) is not caught. This is quite easy to trip if
you are swapping between native and cross building - you get a couple of
errors when you try and build make menuconfig for the first time about
wrong binaries; in my case I just deleted those binaries and did the
make again; however this failure is silent - it just hangs.
A make mrproper is probably the best thing to do when switching - but
the error case needs catching, and I'm sure there are other similar
cases.
Dave
P.S. This was on 2.4.18-rmk7 but I believe it is general.
P.P.S. Is it a good idea to keep binaries in the scripts subdirectory?
---------------- Have a happy GNU millennium! ----------------------
/ Dr. David Alan Gilbert | Running GNU/Linux on Alpha,68K| Happy \
\ gro.gilbert @ treblig.org | MIPS,x86,ARM, SPARC and HP-PA | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
next reply other threads:[~2002-08-24 15:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-24 15:13 Dr. David Alan Gilbert [this message]
2002-08-24 19:21 ` Of hanging menuconfig [cause found] Richard Zidlicky
2002-08-25 9:11 ` Russell King
2002-08-24 20:58 ` Sam Ravnborg
2002-08-24 22:36 ` Dr. David Alan Gilbert
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=20020824151329.GB735@gallifrey \
--to=gilbertd@treblig.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.