Don't use `set pipefail` which is a bashism.
authorTim Newsome <tim@sifive.com>
Fri, 11 Aug 2017 18:15:11 +0000 (11:15 -0700)
committerTim Newsome <tim@sifive.com>
Fri, 11 Aug 2017 18:15:11 +0000 (11:15 -0700)
Instead, just give up on making the log files altogether now. Since
gdbserver.py makes its own log files it's not as necessary in any case.

This is yet another commit in an attempt to get the riscv-tools build to
actually fail if these tests fail.

debug/Makefile

index a5ea832645719116a01f659147fdae417795aeef..d252b550ad6118a260ef41b077f060114905b6f9 100644 (file)
@@ -4,21 +4,19 @@ XLEN ?= 64
 src_dir ?= .
 GDBSERVER_PY = $(src_dir)/gdbserver.py
 
-default: spike$(XLEN).log
+default: spike$(XLEN)
 
-all:   pylint spike32.log spike64.log
+all:   pylint spike32 spike64
 
 pylint:
        pylint --rcfile=pylint.rc `git ls-files '*.py'`
 
-%.log:
-       set -o pipefail; \
+spike%:
        $(GDBSERVER_PY) \
                --isolate \
-               $(src_dir)/targets/RISC-V/$(subst .log,.py,$@) \
+               $(src_dir)/targets/RISC-V/$@.py \
                --sim_cmd $(RISCV)/bin/$(RISCV_SIM) \
                --server_cmd $(RISCV)/bin/openocd \
-           | tee $@ 2>&1 || (sed s/^/$@:\ / $@ && false)
 
 clean:
-       rm -f spike32.log spike64.log *.pyc
+       rm -f *.pyc