buildgcc: improve portability

`cp --remove-destination` isn't as portable as `rm -f` and `cp`.

Change-Id: Ib05bfc121f7a0b467f8104920e14fbd02191585f
Signed-off-by: Jonathan A. Kollasch <jakllsch@kollasch.net>
Reviewed-on: http://review.coreboot.org/150
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
This commit is contained in:
Jonathan A. Kollasch 2011-08-11 14:44:55 -05:00 committed by Patrick Georgi
parent 2aac3f6c51
commit f44bb4f4c1
1 changed files with 2 additions and 1 deletions

View File

@ -463,7 +463,8 @@ printf "Building IASL ${IASL_VERSION} ... "
rm -f .failed
CFLAGS="$HOSTCFLAGS"
$MAKE || touch .failed
cp --remove-destination iasl* $DESTDIR$TARGETDIR/bin || touch .failed
rm -f $DESTDIR$TARGETDIR/bin/iasl || touch .failed
cp iasl $DESTDIR$TARGETDIR/bin || touch .failed
if [ ! -f .failed ]; then touch .success; fi
) &> $IASL_DIR/compiler/crossgcc-build.log
test -r $IASL_DIR/compiler/.failed && printf "${RED}failed${NC}\n" || printf "${green}ok${NC}\n"