diff options
author | Stefan Reinauer <stefan.reinauer@coreboot.org> | 2015-06-09 11:54:49 -0700 |
---|---|---|
committer | Stefan Reinauer <stefan.reinauer@coreboot.org> | 2015-06-09 23:31:22 +0200 |
commit | 916b8455fff116a19d24165267ef0e0011e65a39 (patch) | |
tree | ba0a1a817ef9902a209290114512c5d25b4a366d | |
parent | d0f837239d06b096839dd9133a278c59b7faa3bd (diff) | |
download | coreboot-916b8455fff116a19d24165267ef0e0011e65a39.tar.xz |
buildgcc: Fail if a patch failed to apply
Otherwise one could end up with what they think is a coreboot toolchain
but in fact it'd be missing some patches.
Change-Id: Ic451f7061b822d0f4b64acc9976ba81fd544e85b
Signed-off-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
Reviewed-on: http://review.coreboot.org/10487
Reviewed-by: Patrick Georgi <pgeorgi@google.com>
Tested-by: build bot (Jenkins)
Reviewed-by: Alexander Couzens <lynxis@fe80.eu>
-rwxr-xr-x | util/crossgcc/buildgcc | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/util/crossgcc/buildgcc b/util/crossgcc/buildgcc index 740a0358b9..1f73078b78 100755 --- a/util/crossgcc/buildgcc +++ b/util/crossgcc/buildgcc @@ -226,8 +226,10 @@ unpack_and_patch() { for patch in patches/${dir}_*.patch; do test -r $patch || continue printf " o $(basename $patch)\n" - $PATCH -s -N -p0 < $(echo $patch) || \ + $PATCH -s -N -p0 < $(echo $patch) || { printf "\n${RED}Failed $patch.${NC}\n" + exit 1 + } done touch ${dir}/.unpack_success ) |