On Sat, Nov 10, 2007 at 12:35:01PM -0800, H. Peter Anvin wrote: > > HOWEVER, I think the right thing for allyesconfig, allmodconfig, > randconfig, etc. is to be able to override specific variables. Right > now, one has to use indirection via a file, which is a bit clumsy; it > would be better if one could do "make allyesconfig CONFIG_X86_64=y" or > somesuch.
See patch-set I just sent out :-) > > In fact, we should be able to get rid of ARCH entirely; CONFIG_ options > have the huge advantage that they're saved in a file, and you don't have > to type them on every make run. The only option that I can't see us > getting rid of easily is HOSTCC, since it is used before config is run, > but probably something clever can be done there, too. My long term plan is to enable the above. I had planned to do a lot for 2.6.25 but all this x86 stuff have eaten too much time. And I have plenty of kbuild stuff in my inbox awaiting some attention... Sam - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/