On Wed, 2012-12-26 at 17:52 -0800, David Rientjes wrote:
> On Wed, 26 Dec 2012, David Woodhouse wrote:
> 
> > Thanks. I'll look into this. I presume it was *always* failing, but
> > nobody happened to come across it because our test coverage of x86
> > configs without CONFIG_64BIT wasn't particularly good?
> > 
> 
> Purely for selfish reasons, 32-bit isn't interesting for me.  I'm sure 
> they existed before, as you said, but only got exposed to be because "make 
> randconfig" now allows such configurations.  I've added ARCH=x86_64 to my 
> scripts.

I recommend using an all.config file instead, which will allow you to
set not only the value for CONFIG_64BIT but also anything *else* you
want to exclude. Especially if you want things to actually be bootable,
that will be necessary.

The legacy i386/x86_64 values for $ARCH from before the merge are
basically no longer needed. The *only* thing they do is override the
CONFIG_64BIT setting, IIRC. So they ought to be able to go away in time,
and starting to use them in scripts now is probably not the best idea.

-- 
dwmw2