From bc621bed9c654371a0e8c6e0065f4ea1d79a7c8b Mon Sep 17 00:00:00 2001 From: Sebastian Bauer Date: Thu, 29 Mar 2018 20:57:32 +0200 Subject: [PATCH] Disable the LOG_COMMAND. Piping will have the consequence that the exit status of the first command will not be considered. As this is the compiling command in our case, make will not exit with an error code even if the compiling failed. While there are shell-specific solutions, disabling LOG_COMMAND seems to be the most general solution. --- library/GNUmakefile.os4 | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/library/GNUmakefile.os4 b/library/GNUmakefile.os4 index c232f5b..6fcd170 100644 --- a/library/GNUmakefile.os4 +++ b/library/GNUmakefile.os4 @@ -29,7 +29,11 @@ RANLIB := ppc-amigaos-ranlib COPY := cp -p DELETE := rm -rf MAKEDIR := mkdir -p -LOG_COMMAND := 2>&1 | tee -a compiler.log +# Enabling the LOG_COMMAND has the consequence that a rule will not +# fail on an error because only the exit status from the tee command +# will be considered +#LOG_COMMAND := 2>&1 | tee -a compiler.log +LOG_COMMAND := # You may need to request a specific compiler version in order to # build the baserel versions of the library. At this time of # writing (2008-11-06) GCC 4.0.4 and below support the -mbaserel