Since make is using /bin/sh to execute shell code, avoid the newish
shell construct $() so older (ancient) shells can execute the shell
code in the Makefile.
Signed-off-by: Brandon Casey <redacted>
---
I know that $() is preferred in the main scripts, but the Makefile
is using /bin/sh to execute shell code and there are already a few
places in the Makefile using back-ticks, so it doesn't seem like
going against the flow too much.
Otherwise, should we set the SHELL variable to the configured SHELL_PATH
at some point in the Makefile?
-brandon
Makefile | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
From: Johannes Schindelin <hidden> Date: 2016-06-15 22:45:06
Hi,
On Tue, 5 Aug 2008, Brandon Casey wrote:
Otherwise, should we set the SHELL variable to the configured SHELL_PATH
at some point in the Makefile?
I think that would make more sense, especially since it would catch
wrong SHELL_PATH early.
Maybe we can even have some sanity check that tests if SHELL_PATH groks
$()?
Ciao,
Dscho
This adds a make target which can be used to try to execute certain shell
constructs which are required for compiling and running git.
This patch provides a test for the $() notation for command substition
which is used in the Makefile and extensively in the git scripts.
The make target is named in such a way as to be a hint to the user that
SHELL_PATH should be set to an appropriate shell. If the shell command
fails, the user should receive a message similar to the following:
make: *** [please_set_SHELL_PATH_to_a_more_modern_shell] Error 2
Signed-off-by: Brandon Casey <redacted>
---
Johannes Schindelin wrote:
Maybe we can even have some sanity check that tests if SHELL_PATH groks
$()?
how about this?
-brandon
Makefile | 8 +++++++-
1 files changed, 7 insertions(+), 1 deletions(-)