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/libstdc++-v3/include/c_global/cstdio gcc-4.4.5/libstdc++-v3/include/c_global/cstdio

--- gcc-4.4.5.orig/libstdc++-v3/include/c_global/cstdio	2009-04-10 01:23:07.000000000 +0200

+++ gcc-4.4.5/libstdc++-v3/include/c_global/cstdio	2010-10-09 23:11:27.000000000 +0200

@@ -139,7 +139,7 @@

 _GLIBCXX_END_NAMESPACE

-#if _GLIBCXX_USE_C99

+#if _GLIBCXX_USE_C99 || defined __UCLIBC__

 #undef snprintf

 #undef vfscanf