help-make
[Top][All Lists]
Advanced

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

Re: Looking for well-logged Make output


From: Martin d'Anjou
Subject: Re: Looking for well-logged Make output
Date: Tue, 14 May 2013 18:35:14 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5

Alexander,

When you run make a second time in the same folder, it will continue based on the presence of files, not based on their content. The response from Eric Melski on stackoverflow is right: make sure the output file is created only when the entire recipe has worked.

Martin


On 13-05-14 03:30 PM, Alexander Nelson wrote:
Hello all,

This email is somewhat a cross-post of a Stack Overflow question:
http://stackoverflow.com/questions/16488581/looking-for-well-logged-make-output

The gist is, I run workflows focused on single input files, logging stdout,
stderr and shell exit status of each step.  I think a natural way to
express these workflows is with a Makefile.  However, in the event of an
error (which in my case is more frequently nothing of the program's fault -
the power dies, a disk fills, menial stuff), I'd like Make to be able to
resume a workflow based on the exit status of the intermediary target steps.

That is, if the Make rules include target "target4", I'd like Make to
interpret "target4.status.log" having the contents "0" or "0\n" as "Ok,
target4 built."  But if the log contained anything else, like "1\n" or
"Started", Make would treat that as not-ok and halt.

 From the crickets except one person on Stack Overflow; the gmake man page;
Wikipedia's make-like programs page; and writing a mess of Bash, Python and
Make to do this before; I'm guessing this doesn't exist in any Make.
  However, I figure this list may provide a more authoritative answer.

Has anybody seen something like what I'm asking about before?

--Alex
_______________________________________________
Help-make mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/help-make




reply via email to

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