From: Michal Marek <mmarek@suse.cz>
To: Masahiro Yamada <yamada.m@jp.panasonic.com>,
Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] kbuild: document KBUILD_SHELL
Date: Sat, 05 Jul 2014 00:01:58 +0200 [thread overview]
Message-ID: <53B72456.5050000@suse.cz> (raw)
In-Reply-To: <20140626110242.79E5.AA925319@jp.panasonic.com>
Dne 26.6.2014 04:02, Masahiro Yamada napsal(a):
> On Mon, 9 Jun 2014 13:40:10 +0200
> Sam Ravnborg <sam@ravnborg.org> wrote:
>> All shell scripts that are invoked with $(CONFIG_SHELL) must be sh-compatible,
>> or in practice dash compatible as well as bash compatible.
>> The preference is bash as expressed with the above code.
>
>
> I notice at least two files (scripts/coccicheck and scripts/mkuboot.sh)
> have shebang "#!/bin/bash" even though they are invoked with $(CONFIG_SHELL).
>
> Should we change them to "#!/bin/sh" ?
Sorry for the late reply.
If we are going to change the CONFIG_SHELL (KBUILD_SHELL) variable to
/bin/sh, then yes, please change them to /bin/sh and make them dash
compatible.
> In that case, we also have to modify some lines where bash-extension
> is used.
>
> COCCIINCLUDE=${LINUXINCLUDE//-I/-I }
> COCCIINCLUDE=${COCCIINCLUDE//-include/-I}
>
> I think fixing them is not difficult.
Right, nothing a simple sed call wouldn't fix.
Thanks,
Michal
next prev parent reply other threads:[~2014-07-04 22:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 2:51 [PATCH] kbuild: document KBUILD_SHELL Masahiro Yamada
2014-06-10 9:27 ` Michal Marek
2014-06-10 9:50 ` Sam Ravnborg
2014-06-10 11:00 ` Michal Marek
2014-06-10 11:17 ` Masahiro Yamada
2014-06-10 11:36 ` Michal Marek
2014-06-10 12:02 ` Masahiro Yamada
2014-06-10 12:22 ` Michal Marek
2014-06-10 12:55 ` Masahiro Yamada
2014-06-26 2:02 ` Masahiro Yamada
2014-07-04 22:01 ` Michal Marek [this message]
2014-06-10 19:56 ` Sam Ravnborg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53B72456.5050000@suse.cz \
--to=mmarek@suse.cz \
--cc=linux-kbuild@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=yamada.m@jp.panasonic.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox