URL:
http://savannah.gnu.org/bugs/?33134
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
On Wed, Apr 20, 2011 at 6:03 PM, David Boyce invalid.nore...@gnu.org 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
On Wed, Apr 20, 2011 at 9:58 PM, Philip Guenther guent...@gmail.com 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
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
