AFAIK the binary mode only has effect on Windows but not on POSIX systems, and if stdin is a Linux socket (e.g. when spawned as a Node.js child process), freopen closes it immediately (even if the first argument is NULL) , then otfccbuild hangs after that.
...by making it only
freopenstdin on Windows.AFAIK the binary mode only has effect on Windows but not on POSIX systems, and if stdin is a Linux socket (e.g. when spawned as a Node.js child process),
freopencloses it immediately (even if the first argument isNULL) , thenotfccbuildhangs after that.