Hi Eric, On 11 Mar 2013, at 19:54, Eric Blake <ebl...@redhat.com> wrote: > On 03/10/2013 09:19 PM, Gary V. Vaughan wrote: >> I don't really understand the nuances of this test enough to debug >> any further. It looks like the expectations are too tight by >> requiring an error rather than a silent failure. WDYT? >> > >> ... >> hpux% echo nothing | ./src/m4 >&- >> hpux% echo $? >> 0 > > Hmm. POSIX says that we can't rely on >&- closing stdout; it works on > most platforms, but HPUX apparently ignores the request and reopens > stdout to /dev/null, and POSIX allows this behavior. The test is too > strict, and should be checking whether it is possible to start a program > with stdout closed before requiring a particular behavior in that > condition (since HPUX has no way to get into that condition). > >> Curiously, this test behaves as expected on HPUX-11.11 and 11.00. >> Safe to ignore? Can the test case be fixed? > > I'll see what I can come up with today. If I don't come up with a way, > then it is safe to ignore.
I'm fine with your just making it skip on HPUX >= 11.23 if a portable fix is not straight forward. Cheers, -- Gary V. Vaughan (gary AT gnu DOT org)
