On Sun, Oct 19, 2014 at 01:04:20PM -0700, Linus Torvalds wrote: > On Sun, Oct 19, 2014 at 11:51 AM, Russell King - ARM Linux > <linux@xxxxxxxxxxxxxxxx> wrote: > > > > Does that work for things like allnoconfig and randconfig? I guess people > > /could/ seed those appropriately, but that seems to be something that Olof > > wants to avoid doing. > > You can force particular config options for those, using something like > > export KCONFIG_ALLCONFIG=custom.config > > and filling the custom config file with the required config setting. Yes, this is what I meant above by "seed"ing the configurations, and it is something I do all the time with my autobuilder here for things like allnoconfig where I want to ensure that certain options have specific values. When I talked to Olof about it, he seemed to be against using the facility in his autobuilder. I'm not clear on why that was, but I suspect it's because Olof wants to test real allnoconfig builds. An alternative is we could have a HAVE_GCC_PR58854_FIX preprocessor conditional, and pass in KCFLAGS=-DHAVE_GCC_PR58854_FIX to the kernel to bypass the check. Either way, I think we need Olof's input on this to say what he's willing to do. -- FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up according to speedtest.net. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
