Databases
StackOverflow2013
Postsdbo
POGNU Makefile equivalent of shell 'TRAP' command for concise identification of build failure on exit
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGNU Makefile equivalent of shell 'TRAP' command for concise identification of build failure on exit
    primarykey
    data
    text
    <p>Criteria: Makefile is a GNU Make Makefile - I'm not interested in makepp, qmake, cmake, etc. They're all nice (especially cmake), but this is for work and at work we use GNU Make. The optimal solution is a pure Makefile solution rather than a shell script that parses make for you. </p> <p>I also don't want to do a 'continue on failure' solution - if it's broken, it's broken and needs to be fixed.</p> <p>The situation is this, I've got a makefile that builds several directories in parallel - if one of them fails, of course the whole build fails, but not until all the running makes run to completion (or failure). This means that the reason why make actually failed is buried somewhere arbitrarily far from the end of make's output.</p> <p>Here's an example of what I've got:</p> <pre><code>all: $(SUBDIRS) SUBDIRS = \ apple \ orange \ banana \ pineapple \ lemon \ watermelon \ grapefruit $(SUBDIRS): cd $@ &amp;&amp; $(MAKE) $(MFLAGS) 2&gt;&amp;1 | sed -e "s/^/$(notdir $(@)): /g" </code></pre> <p>If I run 'make -j 5' and 'orange' happens to fail - I'd like to see a table like this at the end of the make process</p> <pre><code> apple - passed orange - FAILED banana - passed pineapple - passed lemon - passed </code></pre> <p>I've considered having an &amp;&amp; echo "passed" >.result || echo "FAILED" >.result, but make still needs some sort of TRAP or __onexit() cleanup command to print at them on exit.</p> <p>Any Makefile ninjas out there have a pure-makefile solution for this? </p> <p>un-edit - my solution wasn't actually working the way I had hoped.. STYMIED!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USsynthesizerpatel
    1. USsynthesizerpatel
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POGNU Makefile equivalent of shell 'TRAP' command for concise identification of build failure on exit
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POGNU Makefile equivalent of shell 'TRAP' command for concise identification of build failure on exit
      1. USRajish
      1. VTFavorite
    3. VO
      singulars
      1. POGNU Makefile equivalent of shell 'TRAP' command for concise identification of build failure on exit
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO"if one of them fails, of course the whole build fails, but not until all the running makes run to completion (or failure)." You can probably improve that situation by prepending `set -o pipefail; ` to the `$(SUBDIRS)` command, so that the nonzero exit code of a failed `$(MAKE)` is no longer hidden by the successful exit of the `sed`.
      singulars
      1. POGNU Makefile equivalent of shell 'TRAP' command for concise identification of build failure on exit
      1. USslowdog
    2. COIf `orange` fails, you want it to proceed with orange, banana, etc.?
      singulars
      1. POGNU Makefile equivalent of shell 'TRAP' command for concise identification of build failure on exit
      1. USBeta
    3. CO@slowdog - The exit code of make isn't necessarily the issue, but thats a good point, +1 for you
      singulars
      1. POGNU Makefile equivalent of shell 'TRAP' command for concise identification of build failure on exit
      1. USsynthesizerpatel
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload