diff options
author | Yann E. MORIN" <yann.morin.1998@free.fr> | 2012-05-08 16:31:10 (GMT) |
---|---|---|
committer | Yann E. MORIN" <yann.morin.1998@free.fr> | 2012-05-08 16:31:10 (GMT) |
commit | f1d6a5cca1a2d21dc5a78d806628625ae0fe6914 (patch) | |
tree | fb9855e066b6636e7be85ad061f184115e7d89b8 /patches/gcc/4.0.4 | |
parent | 91ead3aa8118be45e7bc78d8861f97a8a0c8af7e (diff) |
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>
(transplanted from d48c03998dc1c25a3b29b2c0af425631baee3abe)
Diffstat (limited to 'patches/gcc/4.0.4')
0 files changed, 0 insertions, 0 deletions