aboutsummaryrefslogtreecommitdiff
path: root/libcody
diff options
context:
space:
mode:
authorAlexandre Oliva <oliva@adacore.com>2022-06-03 03:59:01 -0300
committerAlexandre Oliva <oliva@gnu.org>2022-06-03 03:59:01 -0300
commit39ab2e4c3921136136cdb08ca5c81bd0c3fe7d73 (patch)
tree6b11cc6ddcfc560ea0a943d0328ea807b4651520 /libcody
parentb168441c8a6b7cb6b6623694eb9e1cc87a3d51af (diff)
downloadgcc-39ab2e4c3921136136cdb08ca5c81bd0c3fe7d73.zip
gcc-39ab2e4c3921136136cdb08ca5c81bd0c3fe7d73.tar.gz
gcc-39ab2e4c3921136136cdb08ca5c81bd0c3fe7d73.tar.bz2
libcody: fix nonportable shell code in revision.stamp build rule
Two non-portable shell constructs have been long present in libcody's build rule for revision.stamp: $() instead of ``, and += to append to a shell variable. The former seems to work even when bash is operating as /bin/sh, but += doesn't, and it ends up trying to run revision+=M as a command name, and issuing an error as that command is (hopefully) not found. This patch replaces both constructs with more portable ones. for libcody/ChangeLog * Makefile.in (revision.stamp): Replace $() and += with more portable shell constructs.
Diffstat (limited to 'libcody')
-rw-r--r--libcody/Makefile.in4
1 files changed, 2 insertions, 2 deletions
diff --git a/libcody/Makefile.in b/libcody/Makefile.in
index 7eaf8ac..bb87468 100644
--- a/libcody/Makefile.in
+++ b/libcody/Makefile.in
@@ -66,11 +66,11 @@ clean:: Makefile
# FIXME: Delete
revision.stamp: $(srcdir)/.
- @revision=$$(git -C $(srcdir) rev-parse HEAD 2>/dev/null) ;\
+ @revision=`git -C $(srcdir) rev-parse HEAD 2>/dev/null` ;\
if test -n "$$revision" ;\
then revision=git-$$revision ;\
if git -C $(srcdir) status --porcelain 2>/dev/null | grep -vq '^ ' ;\
- then revision+=M ;\
+ then revision=$${revision}M ;\
fi ;\
else revision=unknown ;\
fi ;\