From: Masahiro Yamada <yamada.m@jp.panasonic.com>
To: Michal Marek <mmarek@suse.cz>
Cc: Sam Ravnborg <sam@ravnborg.org>, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] kbuild: document KBUILD_SHELL
Date: Tue, 10 Jun 2014 20:17:07 +0900 [thread overview]
Message-ID: <20140610201706.9614.AA925319@jp.panasonic.com> (raw)
In-Reply-To: <5396E55D.8000202@suse.cz>
Hi Michal, Sam,
On Tue, 10 Jun 2014 13:00:45 +0200
Michal Marek <mmarek@suse.cz> wrote:
> On 2014-06-10 11:50, Sam Ravnborg wrote:
> >>
> >> The variable is assinged with a ":=", not a "?=", so you can't change it
> >> from outside, can you?
> >
> > Variables assigned with ":=" can be changed like this:
> >
> > $ cat Makefile
> > FOO := fisk
> > $(info FOO=$(FOO))
> > all:
> > @:
> >
> > $ FOO=bar make
> > FOO=fisk
> >
> > $ make FOO=bar
> > FOO=bar
> >
> >
> > The first is the same as using an environment variable.
> > The latter is a special make syntax.
>
> I see. But do we want to encourage people to change the value? IMO There
> should be some "change this variable only if you know what you are
> doing" warning.
>
> Michal
IMHO:
If all shell scripts invoked by $KBUILD_SHELL should be sh-compatible,
"KBUILD_SHELL" should always be set to "/bin/sh" and
users should not change it.
I still don't understand why bash is preferable for KBUILD_SHELL.
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2014-06-10 11:17 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 [this message]
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
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=20140610201706.9614.AA925319@jp.panasonic.com \
--to=yamada.m@jp.panasonic.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sam@ravnborg.org \
/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