All,
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.
For example, suppose I run a make, and I find the following from 'make -d'
Successfully remade target file `obj/libcore.dev'.
Finished prerequisites of target file `obj/ld.tr'.
Must remake target `obj/ld.tr'.
./obj/genconf ./obj/devs.tr -h ./obj/gconfxx.h -p "%s&s&&" -pl "&-l%s&s&&" -pL
"&-L%s&s&&" -ol ./obj/ld.tr
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?
Ed
_______________________________________________
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make
