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: http://www.mail-archive.com/commits%40crater.dragonflybsd.org/msg02534.html > Log: > Do not set O_NONBLOCK on a threaded program's descriptors any more. > Instead, use the new system calls to directly issue non-blocking I/O. > Additionally, force blocking I/O for debug output. > > This partly solves the problem of programs such as bmake or gmake > fork/exec'd children which happen to be threaded. The children would > set O_NONBLOCK on e.g. stdin, stdout, and stderr, resulting in > unexpected operation if the unrelated parent program tries to issue a > read or write. > > Solves: gmake 'write error' problem Can anyone expirinced comment this, please? -- Best wishes, Vadim Zhukov
