patches/gcc/4.4.6/220-libiberty-pic.patch
author "Yann E. MORIN" <yann.morin.1998@free.fr>
Tue May 08 18:31:10 2012 +0200 (2012-05-08)
changeset 2964 d48c03998dc1
parent 2149 98b7806295cc
permissions -rw-r--r--
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 diff -durN gcc-4.4.5.orig/libiberty/Makefile.in gcc-4.4.5/libiberty/Makefile.in
     2 --- gcc-4.4.5.orig/libiberty/Makefile.in	2008-10-22 15:30:19.000000000 +0200
     3 +++ gcc-4.4.5/libiberty/Makefile.in	2010-10-09 23:02:28.000000000 +0200
     4 @@ -227,6 +227,7 @@
     5  	  $(AR) $(AR_FLAGS) $(TARGETLIB) \
     6  	    $(REQUIRED_OFILES) $(EXTRA_OFILES) $(LIBOBJS); \
     7  	  $(RANLIB) $(TARGETLIB); \
     8 +	  cp $(TARGETLIB) ../ ; \
     9  	  cd ..; \
    10  	else true; fi
    11