Re: [bug #33134] spurious error when stdout is already closed

2011-04-20 Thread Philip Guenther
On Wed, Apr 20, 2011 at 9:31 PM, David Boyce wrote: > On Thu, Apr 21, 2011 at 12:00 AM, Philip Guenther wrote: >> Why is that a mistake? >> >> It appears you're saying that make should complain about failures to >> write to stdout for reasons like EIO, ENOSPC,  and EOVERFLOW, but >> *not* for EBA

RE: [bug #33134] spurious error when stdout is already closed

2011-04-20 Thread Martin Dorey
> maybe there's a better way of checking for closure than ftell http://software.jessies.org/svn/salma-hayek/trunk/native/all/ruby-launcher/ruby-launcher.cpp suggests: // This might look obscure but the man page suggests that it's a POSIX-compliant way // of testing whether a file descri

Re: [bug #33134] spurious error when stdout is already closed

2011-04-20 Thread David Boyce
On Thu, Apr 21, 2011 at 12:00 AM, Philip Guenther wrote: > Why is that a mistake? > > It appears you're saying that make should complain about failures to > write to stdout for reasons like EIO, ENOSPC,  and EOVERFLOW, but > *not* for EBADF. I think you're still not getting my point here. I do no

Re: [bug #33134] spurious error when stdout is already closed

2011-04-20 Thread Philip Guenther
On Wed, Apr 20, 2011 at 7:36 PM, David Boyce wrote: > On Wed, Apr 20, 2011 at 9:58 PM, Philip Guenther wrote: >> Could you explain why you think that's spurious?  Make wanted to write >> "date" to stdout and the write failed.  Seems legit to me. ... > Basically in a (sensible and nicely documente

Re: [bug #33134] spurious error when stdout is already closed

2011-04-20 Thread David Boyce
On Wed, Apr 20, 2011 at 9:58 PM, Philip Guenther wrote: > Could you explain why you think that's spurious?  Make wanted to write > "date" to stdout and the write failed.  Seems legit to me. That's actually not what generates the error message. I'm not sure why it doesn't happen the way you say, b

Re: [bug #33134] spurious error when stdout is already closed

2011-04-20 Thread Philip Guenther
On Wed, Apr 20, 2011 at 6:03 PM, David Boyce wrote: ... > Ironically, make's attempt to be super-duper careful about catching write > errors to stdout (in the close_stdout function) results in a spurious error > message when the user has already closed stdout: > > % cat makefile > .PHONY: all > al

[bug #33134] spurious error when stdout is already closed

2011-04-20 Thread David Boyce
URL: Summary: spurious error when stdout is already closed Project: make Submitted by: boyski Submitted on: Thu 21 Apr 2011 01:03:09 AM GMT Severity: 3 - Normal Item Grou