diff options
| author | Alexandre Oliva <oliva@adacore.com> | 2022-06-03 03:59:01 -0300 |
|---|---|---|
| committer | Alexandre Oliva <oliva@gnu.org> | 2022-06-03 03:59:01 -0300 |
| commit | 39ab2e4c3921136136cdb08ca5c81bd0c3fe7d73 (patch) | |
| tree | 6b11cc6ddcfc560ea0a943d0328ea807b4651520 /gcc | |
| parent | b168441c8a6b7cb6b6623694eb9e1cc87a3d51af (diff) | |
| download | gcc-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 'gcc')
0 files changed, 0 insertions, 0 deletions