EPICS Home

Experimental Physics and Industrial Control System


 
2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <20202021  2022  2023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <20202021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: GNU Make option --trace
From: "Johnson, Andrew N. via Core-talk" <core-talk at aps.anl.gov>
To: EPICS core-talk <core-talk at aps.anl.gov>
Date: Fri, 21 Aug 2020 22:15:15 +0000
I just come across the --trace flag to gnumake (added in 4.0) which I suspect might have been very useful in all sorts of circumstances debugging the build rules if I’d known about it:

From the NEWS file:

* New command line option: --trace enables tracing of targets.  When enabled
  the recipe to be invoked is printed even if it would otherwise be suppressed
  by .SILENT or a "@" prefix character.  Also before each recipe is run the
  makefile name and linenumber where it was defined are shown as well as the
  prerequisites that caused the target to be considered out of date.

@Michael, when you next get a build loop, please try adding this flag to help us figure out what’s going on.

- Andrew

-- 
Complexity comes for free, simplicity you have to work for.


Navigate by Date:
Prev: [Bug 1884339] Re: Inaccessible CA servers on Windows Andrew Johnson via Core-talk
Next: Build failed: epics-base base-dynamic-rRDD-580 AppVeyor via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <20202021  2022  2023  2024 
Navigate by Thread:
Prev: Jenkins build is back to stable : epics-pvAccess-mac #412 APS Jenkins via Core-talk
Next: Build failed: epics-base base-dynamic-rRDD-580 AppVeyor via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <20202021  2022  2023  2024