1 |
Hey :) |
2 |
|
3 |
i just had some good time (since yesterday), trying to find out why |
4 |
portage (14555) behaves quite strange. what i was seeing was this: |
5 |
|
6 |
i start emerge -av1 expat on winnt (so interix portage): |
7 |
|
8 |
1) it starts, verifies things, etc. |
9 |
2) it eautoreconfs |
10 |
3) it starts configure. |
11 |
4) somewhere at "checking whether the C compiler works ..." it seems to stop |
12 |
5) after some seconds, portage fails with "make failed" (!). |
13 |
|
14 |
looking at the config.log for that package, configure finished |
15 |
successfully (!). |
16 |
|
17 |
after digging through the diffs to the last working portage version |
18 |
(14487), i found out that adding "Interix" to the platforms where |
19 |
portage should _not_ disable openpty, things return back to working. |
20 |
|
21 |
it seems that the code using os.pipe() seems either broken or the |
22 |
interix implementation of that python code is broken... whichever it is |
23 |
- it's bad ... :( |
24 |
|
25 |
Could you (grobian), please add "Interix" to the existing white list for |
26 |
openpty platforms? |
27 |
|
28 |
Cheers, Markus |