"Paul D. Smith" <[EMAIL PROTECTED]> writes:
> pjl> That is, when the job is being placed on the waiting chain
> pjl> because the load is too high, start_job_command() is never
> pjl> called.
>
> That's not true, though: you didn't examine what happens to those jobs
> _after_ they get put o
%% Patrick Craig <[EMAIL PROTECTED]> writes:
pc> GNU Make version 3.79.1
pc> Built for i686-pc-cygwin
pc> My project has some autogenerated C files. I use a different
pc> suffix for these files (.agc) so that I can delete them in the
pc> clean rule (rm -f *.agc). Here is a simplified
%% "Patrick J. LoPresti" <[EMAIL PROTECTED]> writes:
pjl> I have attached a Makefile to the end of this message which
pjl> illustrates this bug.
I will look at the bug, but offhand your description of the code is
missing something important (or, I misunderstood you).
pjl> The problem is t
I have attached a Makefile to the end of this message which
illustrates this bug. Make should exit successfully when run on this
Makefile, but it does not if you invoke it like this (assuming your
load average is greater than zero):
rm -f Makefile2 Makefile3 ; make -j 2 -l 0.0
The problem is
