[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: FWD: Re: 3.81 and windows paths

From: Eli Zaretskii
Subject: Re: FWD: Re: 3.81 and windows paths
Date: Fri, 28 Jul 2006 16:47:46 +0300

> Date: Fri, 28 Jul 2006 08:53:06 -0400
> From: Earnie Boyd <address@hidden>
> Cc: address@hidden, address@hidden
> I wanted to be able to use the ``native'' version of make with 
> MSYS but I've found that if make creates a configure process and I 
> interrupt make with CTRL-C then the configure script continues to 
> execute.

Is that in Make 3.81?  If so, it could be that the necessary code is
not compiled somehow in your native Windows binary.

The problem is that, when you interrupt a console application on
Windows, the OS creates a new thread and runs the signal handler
inside that thread, while the main thread continues to run.  In Make
3.81, I added special code that stops the main thread in its tracks
when the signal handler is entered.  The two parts of this code are in
job.c (search for GetCurrentThread) and in commands.c, in the function
fatal_error_signal.  Both places condition the code on WINDOWS32;
perhaps your build somehow skipped that.

Alternatively, maybe the MSYS port of Bash does something that results
in this strange behavior.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]