Hey  :)

i just had some good time (since yesterday), trying to find out why
portage (14555) behaves quite strange. what i was seeing was this:

i start emerge -av1 expat on winnt (so interix portage):

1) it starts, verifies things, etc.
2) it eautoreconfs
3) it starts configure.
4) somewhere at "checking whether the C compiler works ..." it seems to stop
5) after some seconds, portage fails with "make failed" (!).

looking at the config.log for that package, configure finished
successfully (!).

after digging through the diffs to the last working portage version
(14487), i found out that adding "Interix" to the platforms where
portage should _not_ disable openpty, things return back to working.

it seems that the code using os.pipe() seems either broken or the
interix implementation of that python code is broken... whichever it is
- it's bad ...  :(

Could you (grobian), please add "Interix" to the existing white list for
openpty platforms?

Cheers, Markus