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 -ur uClibc-0.9.29/libc/inet/resolv.c uClibc-0.9.29-patched/libc/inet/resolv.c

 --- uClibc-0.9.29/libc/inet/resolv.c	2007-04-23 12:01:05.000000000 -0500

 +++ uClibc-0.9.29-patched/libc/inet/resolv.c	2007-05-09 18:05:33.563404419 -0500

 @@ -1700,7 +1700,7 @@

  int gethostent_r(struct hostent *result_buf, char *buf, size_t buflen,

  	struct hostent **result, int *h_errnop)

  {

 -    int ret;

 +    int ret = HOST_NOT_FOUND;

      __UCLIBC_MUTEX_LOCK(mylock);

      if (__gethostent_fp == NULL) {