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