crosstool-ng: patches/gcc/4.3.1/170-libiberty-pic.patch@d48c03998dc1

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>

     1 Original patch from gentoo: gentoo/src/patchsets/gcc/4.3.1/gentoo/51_all_gcc-3.4-libiberty-pic.patch

     2 diff -durN gcc-4.3.1.orig/libiberty/Makefile.in gcc-4.3.1/libiberty/Makefile.in

     3 --- gcc-4.3.1.orig/libiberty/Makefile.in	2007-07-25 08:26:45.000000000 +0200

     4 +++ gcc-4.3.1/libiberty/Makefile.in	2008-06-10 14:58:02.000000000 +0200

     5 @@ -225,6 +225,7 @@

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

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

     8  	  $(RANLIB) $(TARGETLIB); \

     9 +	  cp $(TARGETLIB) ../ ; \

    10  	  cd ..; \

    11  	else true; fi

author	"Yann E. MORIN" <yann.morin.1998@free.fr>
	Tue May 08 18:31:10 2012 +0200 (2012-05-08)
changeset 2964	d48c03998dc1
parent 746	b150d6f590fc
permissions	-rw-r--r--