On Sun, 2014-07-06 at 14:02 +0400, Konstantin Khlebnikov wrote: > On Sun, Jul 6, 2014 at 1:08 PM, Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> wrote: > > On Sun, Jul 6, 2014 at 11:05 AM, Paul Bolle <pebolle@xxxxxxxxxx> wrote: > >> Could the same result be had by saving CONFIG_ARCH in .config (I suppose > >> it actually already is) and then use its value on builds with > > > > No, currently it's not saved in .config, so I guess that's why this convoluted > > approach is needed. > > Yep, kconfig neither reads nor writres symbols with option env=... > > > > >> that .config unless ARCH is specified in the environment again? Ie, > >> change the "option env=[...]" semantics a bit, perhaps by special casing > >> CONFIG_ARCH. > > > > Indeed. > > If it's saved in config value might be out of sync with actual environment: > ARCH != CONFIG_ARCH. So, behaviour becomes too complicated. So let the environment overrules what is saved in the .config. What makes that complicated? Paul Bolle -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
