[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <831ebaf6-6fea-65ea-aa60-c47f6f05dbb0@gmail.com>
Date: Fri, 19 Aug 2022 15:58:40 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Masahiro Yamada <masahiroy@...nel.org>,
linux-kbuild@...r.kernel.org
Cc: Nick Desaulniers <ndesaulniers@...gle.com>,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
Randy Dunlap <rdunlap@...radead.org>,
Richard Purdie <richard.purdie@...uxfoundation.org>,
Jonathan Corbet <corbet@....net>,
Michal Marek <michal.lkml@...kovi.net>,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 2/3] kconfig: allow to choose the shell for $(shell )
functions
On 8/19/22 13:56, Masahiro Yamada wrote:
> GNU Make uses /bin/sh by default for running recipe lines and $(shell )
> functions. You can change the shell by setting the 'SHELL' variable.
> Unlike most variables, 'SHELL' is never set from the environment. [1]
>
> Currently, Kconfig does not provide any way to change the default shell.
> /bin/sh is always used for running $(shell,...) because do_shell() is
> implemented by using popen(3).
>
> This commit allows users to change the shell for Kconfig in a similar
> way to GNU Make; you can set the 'SHELL' variable in a Kconfig file to
> override the default shell. It is not taken from the environment. The
> change is effective only for $(shell,...) invocations called after the
> 'SHELL' assignment.
>
Hmmm...
Can we say that if we run SHELL=/bin/bash make nconfig, Kconfig will use
$SHELL but we can't set it as environment variable?
--
An old man doll... just what I always wanted! - Clara
Powered by blists - more mailing lists