diff options
author | Masahiro Yamada <yamada.masahiro@socionext.com> | 2019-08-25 22:28:37 +0900 |
---|---|---|
committer | Masahiro Yamada <yamada.masahiro@socionext.com> | 2019-09-04 22:54:13 +0900 |
commit | 858805b336be1cabb3d9033adaa3676574d12e37 (patch) | |
tree | 3b276a719e3c841889b6924c18622bcaf87c9399 /init | |
parent | 8cc7af751443f7c82d12c7e5061fd2fa2e08a3d4 (diff) | |
download | linux-858805b336be1cabb3d9033adaa3676574d12e37.tar.gz |
kbuild: add $(BASH) to run scripts with bash-extension
CONFIG_SHELL falls back to sh when bash is not installed on the system, but nobody is testing such a case since bash is usually installed. So, shell scripts invoked by CONFIG_SHELL are only tested with bash. It makes it difficult to test whether the hashbang #!/bin/sh is real. For example, #!/bin/sh in arch/powerpc/kernel/prom_init_check.sh is false. (I fixed it up) Besides, some shell scripts invoked by CONFIG_SHELL use bash-extension and #!/bin/bash is specified as the hashbang, while CONFIG_SHELL may not always be set to bash. Probably, the right thing to do is to introduce BASH, which is bash by default, and always set CONFIG_SHELL to sh. Replace $(CONFIG_SHELL) with $(BASH) for bash scripts. If somebody tries to add bash-extension to a #!/bin/sh script, it will be caught in testing because /bin/sh is a symlink to dash on some major distributions. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Diffstat (limited to 'init')
0 files changed, 0 insertions, 0 deletions