Re: Of hanging menuconfig [cause found]

[Richard Zidlicky <rz@linux-m68k.org>]

On Sat, Aug 24, 2002 at 04:13:29PM +0100, Dr. David Alan Gilbert wrote:
> 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.

look at dmesg and add an
	alias binfmt-xxxx off
to /etc/modules.conf so similar problems get caught properly - unless 
you want to actually use an emulator for this architecture of course :)

This is one of the cases where I wish kmod would do something more 
intelligent by default than endless loop. Would it be a good idea 
to attempt loading of emulator modules only for formats that are 
previously somehow registered + a few well known like aout,misc,elf?

Looking at exec.c, why isn't the result of request_module() tested?

Richard