scripts: fix catching failures

POSIX 1003.1-2008 does not say whether "set -e" should catch a sub-shell
that exits with !0 (it has a list of conditions to catch, but no list of
conditions not to catch, and this situation is not listed).

bash-3 does not catch such a failure, but bash-4 does. That why, on my
Squeeze system I did not see the issue, while Thomas did on is Lenny chroot.

Reported-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>

diff -durN gcc-4.4.5.orig/libiberty/Makefile.in gcc-4.4.5/libiberty/Makefile.in

--- gcc-4.4.5.orig/libiberty/Makefile.in	2008-10-22 15:30:19.000000000 +0200

+++ gcc-4.4.5/libiberty/Makefile.in	2010-10-09 23:02:28.000000000 +0200

@@ -227,6 +227,7 @@

 	  $(AR) $(AR_FLAGS) $(TARGETLIB) \

 	    $(REQUIRED_OFILES) $(EXTRA_OFILES) $(LIBOBJS); \

 	  $(RANLIB) $(TARGETLIB); \

+	  cp $(TARGETLIB) ../ ; \

 	  cd ..; \

 	else true; fi