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>

 source "config/configure.in"

 source "config/backend.in"

 source "config/global.in"

 source "config/target.in"

 source "config/toolchain.in"

 source "config/kernel.in"

 source "config/binutils.in"

 source "config/cc.in"

 source "config/libc.in"

 source "config/debug.in"

 source "config/companion_libs.in"

 source "config/companion_tools.in"

 source "config/test_suite.in"