From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cpsmtpb-ews01.kpnxchange.com ([213.75.39.4]:49717 "EHLO cpsmtpb-ews01.kpnxchange.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750904AbaGFKTU (ORCPT ); Sun, 6 Jul 2014 06:19:20 -0400 Message-ID: <1404641957.24853.14.camel@x220> Subject: Re: [PATCH] kconfig: store default ARCH in .config From: Paul Bolle Date: Sun, 06 Jul 2014 12:19:17 +0200 In-Reply-To: References: <20140706080234.19520.96704.stgit@zurg> <1404637557.24853.12.camel@x220> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kbuild-owner@vger.kernel.org List-ID: To: Konstantin Khlebnikov Cc: Geert Uytterhoeven , Michal Marek , "linux-kernel@vger.kernel.org" , linux-kbuild , Greg Kroah-Hartman , Andrew Morton , Linus Torvalds , "linux-arm-kernel@lists.infradead.org" On Sun, 2014-07-06 at 14:02 +0400, Konstantin Khlebnikov wrote: > On Sun, Jul 6, 2014 at 1:08 PM, Geert Uytterhoeven wrote: > > On Sun, Jul 6, 2014 at 11:05 AM, Paul Bolle 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