On Wed, Aug 03, 2016 at 03:03:59PM -0400, Paul Gortmaker wrote: > Only one defconfig has a STACKPROTECTOR value. And it asks for > the strong variant, which isn't supported by older toolchains. > > Due to the nature of MIPS having more platform specific code than say > x86, the allyesconfig and allmodconfig aren't as effective for build > coverage. So, in addition, I like to use a trivial script to walk all > the defconfigs and build each one. > > However I will get false positives on unsupported stackprotector values > with an older toolchain like gcc-4.6.3. As in this instance I am just > using the compiler as a glorified syntax checker on a machine where I > build a bunch of other arch for the same reason, there is no real > motivation to get a newer toolchain for improved optimization etc. > > Since there is only one of them, and there is nothing about these > settings that are board/platform specific, I propose we just eliminate > the existing instance and take the default. Yeah, I can see how that one may get annoying. I wish there was something along the lines of KCONFIG_ALLCONFIG that was working not only for allyesconfig/allmodconfig/allnoconfig/randconfig. Applied. Thanks, Ralf
