From d1adafec0507109629fa4d1005e510a3234e04fb Mon Sep 17 00:00:00 2001 From: Alexander Couzens Date: Wed, 21 Oct 2015 12:02:39 +0200 Subject: cpu: create an empty file when no microcode files are given Having an empty microcode file makes it more easy to debug in comparison to a not existing file in cbfs. There are some platforms (e.g. ep80579) which support microcode updates but not having any microcode updates yet in our tree. These platform hang the build because `cat` is called with no parameters. Change-Id: I2699bde0c62ae62ca888686f8b496e845c36d970 Signed-off-by: Alexander Couzens Reviewed-on: http://review.coreboot.org/12109 Tested-by: build bot (Jenkins) Reviewed-by: Nico Huber Reviewed-by: Patrick Georgi Reviewed-by: Paul Menzel --- src/cpu/Makefile.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/cpu/Makefile.inc b/src/cpu/Makefile.inc index d9390610c662..52b58f7ecba7 100644 --- a/src/cpu/Makefile.inc +++ b/src/cpu/Makefile.inc @@ -40,7 +40,7 @@ endif $(obj)/cpu_microcode_blob.bin: $$(cpu_microcode_bins) @printf " MICROCODE $(subst $(obj)/,,$(@))\n" @echo $(cpu_microcode_bins) - cat $+ > $@ + cat /dev/null $+ > $@ cbfs-files-$(cbfs_include_ucode) += cpu_microcode_blob.bin cpu_microcode_blob.bin-file := $(cpu_ucode_cbfs_file) -- cgit v1.2.3