[lkml]   [2002]   [Aug]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Of hanging menuconfig [cause found]
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.
This does not make sense...
lxdialog are compiled utilising HOSTCC, and HOSTCC always points to gcc.
So unless you fail to keep gcc for native in PATH and use:
$> make CROSS_COMPILE=arm all
to do cross-compile the above scenario should not be possible.
In other words
$> which gcc
shall always point to the gcc used for native architecture. Cross
compiling are done by specifying another gcc using the above syntax.
[I've only looked in 2.5 sources by the way, 2.4 may differ here].

Another point is that the current kbuild is too weak when architecture
is changed. Changing architecture should require a make mrproper.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:28    [W:0.070 / U:0.508 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site