Date: Sun, 05 May 2013 20:17:50 +0300
From: Eli Zaretskii e...@gnu.org
Cc: bug-make@gnu.org
From: Paul Smith psm...@gnu.org
Cc: bug-make@gnu.org
Date: Sun, 05 May 2013 12:56:48 -0400
On Sun, 2013-05-05 at 19:36 +0300, Eli Zaretskii wrote:
However, I wonder what was the reason
From: Paul Smith p...@mad-scientist.net
Cc: bug-make@gnu.org
Date: Sat, 04 May 2013 17:51:05 -0400
Eli, I did some cleanup in job.c to try to make things simpler and
reduce duplication. I tried to be careful but it's quite possible I did
something to disrupt the Windows version again.
On Sun, 2013-05-05 at 19:36 +0300, Eli Zaretskii wrote:
However, I wonder what was the reason for splitting the definition of
GMK_EXPORT in two, and putting each part in a different file.
Well, because the gnumake.h file is intended to be installed into the
user's /usr/include or similar, and
From: Paul Smith psm...@gnu.org
Cc: bug-make@gnu.org
Date: Sun, 05 May 2013 12:56:48 -0400
On Sun, 2013-05-05 at 19:36 +0300, Eli Zaretskii wrote:
However, I wonder what was the reason for splitting the definition of
GMK_EXPORT in two, and putting each part in a different file.
Well,
From: Paul Smith psm...@gnu.org
Cc: stefano.lattar...@gmail.com, bug-make@gnu.org
Date: Fri, 03 May 2013 17:17:44 -0400
-O in no way changes that behavior, all it does is ensure that output
from any individual line or target of the recipe will not interfere with
any other individual line
On Fri, 2013-05-03 at 12:55 -0400, Paul Smith wrote:
Suppose we do this: if we're about to invoke a line marked recursive
and we're in -Otarget mode, then before we run it we'll show the
current contents of the temp file (using the normal synchronized
output function).
I've implemented this
I have a solution for this problem that I think will work well, and will
be simple to implement.
Suppose we do this: if we're about to invoke a line marked recursive and
we're in -Otarget mode, then before we run it we'll show the current
contents of the temp file (using the normal synchronized