No it's not cygwin, and as I said I already googled it.
But I will say the current mechanism is not POSIX compliant. Gentoo is using a Linux'ism here and it's not portable. Opening a fifo in read/write mode has nondeterministic behavior in POSIX.
Should I log this as a bug ? Alan. On 10/05/13 08:04, Greg Turner wrote:
If you're running portage under cygwin, somehow, you'll want to replace the multijob eclass and multijob portage-internal bash script with equivalent noop stubs. Cygwin has broken named pipe handling, blah blah blah... Google it. But you'll need a LOT more than that to make it work! I tried pretty hard for a couple of years to get it working and at some points managed to get most of '@system' working -- but never without gross hacks. See my github if interested (but be advised it has not received any love for a long time and is surely of extremely limited utility by now). There probably are no cygwin people. The cygwin profile in portage is for a super old version if that's what you're using, btw -- what you get with that is more akin to "msys" than present-day cygwin. -gmt
