On Tue, Jun 11, 2013 at 10:52:16AM +0100, Markos Chandras wrote: (Adding the kconfig maintainer and mailing list to cc.) > Certain randconfigs may not select neither CONFIG_32BIT nor > CONFIG_64BIT which can lead to build problems and to the following > Kbuild warning: > > .config:154:warning: symbol value '' invalid for PHYSICAL_START > > Signed-off-by: Markos Chandras <markos.chandras@xxxxxxxxxx> > Acked-by: Steven J. Hill <Steven.Hill@xxxxxxxxxx> Systems are supposed to set if they support 32 bit kernels and/or 64 bit kernels in arch/mips/Kconfig. The behaviour you're reporting happens if the default system (which happens to be SGI_IP22) supports both kernel models, that is SYS_SUPPORTS_32BIT_KERNEL and SYS_SUPPORTS_64BIT_KERNEL are set. Then "make randconfig" will generate a .config with neiher CONFIG_32BIT nor CONFIG_64BIT set. Just defaulting to CONFIG_32BIT as in your patch http://patchwork.linux-mips.org/patch/5377/ isn't really a good solution because for some platforms 32 bit kernels, for others 64 bit kernels are preferred so I tried to implement something like choice prompt "Kernel code model" default 32BIT if SYS_32BIT_KERNEL_PREFERRED default 64BIT if SYS_64BIT_KERNEL_PREFERRED and have individual platforms set their preferred kernel variant. And I got more odd Kconfig behaviour, getting both choice values 32BIT and 64BIT set for some platforms. Another variant that only uses a single auxilliary symbol, SYS_64BIT_KERNEL_PREFERRED like this: choice prompt "Kernel code model" default 32BIT if !SYS_64BIT_KERNEL_PREFERRED default 64BIT if SYS_64BIT_KERNEL_PREFERRED still results in CONFIG_32BIT=y CONFIG_64BIT=y So I'm not quite certain how to obtain the desired behaviour - but I appears highly unobvious to buggy on kconfig's side. Michal, can you shed some light? Ralf
