gmake write error and possible solution

Hello all. Putting this on a misc@ list because this looks like not the port problem itself. Recently I start running (too) often in GMake's write error problem. It was reported some times ago here with no result. And after some more digging I found that commit in DragonFlyBSD:

Re: gmake write error and possible solution

On Tue, Jan 6, 2009 at 6:47 PM, Vadim Zhukov persg...@gmail.com wrote: Recently I start running (too) often in GMake's write error problem. It was reported some times ago here with no result. And after some more digging I found that commit in DragonFlyBSD:

Re: gmake write error and possible solution

On Tue, Jan 6, 2009 at 5:07 PM, Ted Unangst ted.unan...@gmail.com wrote: ... Let me qualify that. The reason for the maybe is that there can be many reasons for a program to set stdout to non-blocking. It may not always be the result of pthread fiddling. So gmake is still wrong. If its

Re: gmake write error and possible solution

On Tue, Jan 6, 2009 at 8:51 PM, Philip Guenther guent...@gmail.com wrote: As for this being a bug in gmake, well, the same bug exists in *lots* of programs. I used to hit it all the time with the system 'vi' when debugging a threaded program that crashed, leaving the session's std{in,out,err}