Quoting Edward Peschko <e...@yahoo-inc.com>:
I've been using make for a while now, and one thing that has always
bothered me is the inability to track down problems by reverse
engineering output.
...
My question - how do you actually trace this back to the target that
generated this statement? In this case, the ghostscript Makefile is
so convoluted that it goes through levels of indirection to get to
this point, so grep is of limited help here.
So - why can't make add (optionally, of course) a line number/file
name combo to each of the statements that it executes - and as an
additional option show the text of the makefile that is executing at
the time?
See recent thread:
http://lists.gnu.org/archive/html/bug-make/2010-07/msg00159.html
http://lists.gnu.org/archive/html/bug-make/2010-08/msg00002.html
Summary:
The feature you describe would indeed be a nice thing to add.
It's possible to simulate it at present if your make-files are nicely
written, but tiresome if you're dealing with someone else's make files
that didn't contemplate the need to do this.
Eddy.
_______________________________________________
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make
