On 25 April 2013 20:06, Eli Zaretskii e...@gnu.org wrote:
Date: Thu, 25 Apr 2013 19:36:28 +0100
From: Tim Murphy tnmur...@gmail.com
Cc: bug-make@gnu.org bug-make@gnu.org
1) sem_timedwait() in posix lets you timeout so in a big build when
something crashes or just sits around, there
Date: Fri, 26 Apr 2013 09:05:18 +0100
From: Tim Murphy tnmur...@gmail.com
Cc: Paul D. Smith psm...@gnu.org, bug-make@gnu.org bug-make@gnu.org
How much would you use for the timeout, though? A sub-Make could
legitimately run for a very long time, depending on what's in the
Makefile.
-- Forwarded message --
From: Tim Murphy tnmur...@gmail.com
Date: 25 April 2013 07:13
Subject: Re: [bug #33138] .PARLLELSYNC enhancement with patch
To: Paul D. Smith psm...@gnu.org
To be honest, I have done all this before with named semaphores including
the file that gets left
On Thu, 2013-04-25 at 07:14 +0100, Tim Murphy wrote:
To be honest, I have done all this before with named semaphores
including the file that gets left over problem and it's all solvable
quite nicely. You pass the build id in the environment which is,
after all, what it's for.
Sure. Given
Ok, I don't want to be too much of a pain - I can see the way things have
gone and my attitude is oh well but I thought I'd put the case anyhow:
1) sem_timedwait() in posix lets you timeout so in a big build when
something crashes or just sits around, there is at least the option of
printing an
Date: Thu, 25 Apr 2013 19:36:28 +0100
From: Tim Murphy tnmur...@gmail.com
Cc: bug-make@gnu.org bug-make@gnu.org
1) sem_timedwait() in posix lets you timeout so in a big build when
something crashes or just sits around, there is at least the option of
printing an error message or giving up
