autoconf-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [SCM] GNU Autoconf source repository branch, master, updated. v2.63b


From: Paolo Bonzini
Subject: Re: [SCM] GNU Autoconf source repository branch, master, updated. v2.63b-70-g9c25a39
Date: Sun, 12 Jul 2009 13:18:16 +0200
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b3pre) Gecko/20090513 Fedora/3.0-2.3.beta2.fc11 Lightning/1.0pre Thunderbird/3.0b2

On 07/11/2009 10:11 AM, Ralf Wildenhues wrote:
* Eric Blake wrote on Thu, Jul 09, 2009 at 02:25:49PM CEST:
According to Ralf Wildenhues on 7/9/2009 12:19 AM:
@@ -994,7 +994,8 @@ AT_CHECK([${CONFIG_SHELL-$SHELL} -c 'test -n 
"${BASH_VERSION+set}]]dnl
  [[${ZSH_VERSION+set}${TEST_PARALLEL_AUTOTEST+set}"' || exit 77])
  # The parallel scheduler requires mkfifo and job control to work.
  AT_CHECK([mkfifo fifo || exit 77])
-AT_CHECK([${CONFIG_SHELL-$SHELL} -c '(set -m&&  set +m) || exit 77'])
+AT_CHECK([${CONFIG_SHELL-$SHELL} -c '(set -m&&  set +m) || exit 77'],
+        [], [], [ignore])
Hmm, shouldn't we also ignore stderr if mkfifo fails?

Hmm, probably; but I haven't encountered that issue.  Is it documented
unclearly, or implemented wrongly, that an exit status of 77 does not
override a mismatched stdout/stderr with AT_CHECK?

The implementation is correct. First at_fn_check_status exits if the test's exit status 77. Then at_failed is checked and at_fn_log_failure is invoked if it is true, but at this point we already exited.

Paolo




reply via email to

[Prev in Thread] Current Thread [Next in Thread]