This is the mail archive of the
mailing list for the Cygwin project.
Re: Cygwin: Problem detecting subprocess termination after _spawn_posix in distutils?
- From: Steve Holden <steve at holdenweb dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 14 Sep 2007 02:00:20 -0400
- Subject: Re: Cygwin: Problem detecting subprocess termination after _spawn_posix in distutils?
- References: <firstname.lastname@example.org> <46AFAD41.email@example.com> <46AFDF97.firstname.lastname@example.org> <46B01E90.email@example.com> <46B06554.firstname.lastname@example.org> <46CA2F20.email@example.com>
Steve Holden wrote:
Steve Holden wrote:
[Python interpreter hanging during distutils install of Python imaging
Martin v. Löwis wrote:
A further data point (sorry, I've not had a lot of time to look at
this). Building Python from the trunk at rev 57076 yielded a system that
*would* cleanly build the same release of PIL. This is somewhat annoying
because it appears to put the bug in the past where there's less
incentive to investigate it. But I may find time to take a look.
I updated Cygwin and did a rebaseall before posting.
The only environment variables that don't appear in the shell output
from the env command are INFOPATH, MAKE_MODE and PLAT. I am still
At this point, I'd recommend to perform a cygwin update; with Cygwin,
these problems often go away with an update.
I posted on Cygwin before asking here.
If that doesn't help, you can ask on the Cygwin list also; to analyse
this further, ISTM one will need to debug the internals of cygwin.
I'll do that, though I have reason to believe the gcc *is* terminating
and _spawn_posix isn't detecting the end of the process. At the very
least we should get another test out of this dreadfully irritating bug.
One thing you could try is to add -v to the list of gcc options;
you can then see whether gcc is progressing correctly.
Thanks again for looking at this.
Hardly worth it if I'm the only one noticing the issue, though.
Yet another piece of information. I recompiled the Python 2.5.1
interpreter and ran the library install using the just-built interpreter
from the location it was built in. This ran perfectly fine (and happily
resulted in a usable 2.5 library).
The strange thing is that when I installed the same interpreter,
replacing the standard one in /usr/bin, it too failed in the same way.
Can anyone think of anything that might have affected the interpreter's
ability to detect subprocess termination? This is bugging the heck out
Steve Holden +1 571 484 6266 +1 800 494 3119
Holden Web LLC/Ltd http://www.holdenweb.com
Skype: holdenweb http://del.icio.us/steve.holden
--------------- Asciimercial ------------------
Get on the web: Blog, lens and tag the Internet
Many services currently offer free registration
----------- Thank You for Reading -------------
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html