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>

# Overall toolchain configuration: paths, jobs, etc...

# Allow unconditional usage of tristates

config MODULES

    bool

    default y

menu "Paths and misc options"

source "config/global/ct-behave.in"

source "config/global/paths.in"

source "config/global/download.in"

source "config/global/extract.in"

source "config/global/build-behave.in"

source "config/global/logging.in"

endmenu