Re: debugging feature for recursive rules

2009-04-18 Thread Karl Berry
Very good. Minor comments: * Hard-Coded Install Paths::Installing to Hard-Coded Locations Wrong capitalization in the menu description this time, should be "hard-coded locations". +don't work as expected. Besides debug options provided by the Suggest inserting "the" after "Beside

Re: debugging feature for recursive rules

2009-04-18 Thread Ralf Wildenhues
* Karl Berry wrote on Sat, Apr 18, 2009 at 08:57:36PM CEST: > Try `make SHELL="/bin/bash -vx"', that should help for all rules that > > Good suggestion. Perhaps it should be added to the manual, if you > didn't already. You mean like this? Thanks, Ralf 2009-04-18 Ralf Wildenhues

Re: debugging feature for recursive rules

2009-04-18 Thread Karl Berry
Try `make SHELL="/bin/bash -vx"', that should help for all rules that Good suggestion. Perhaps it should be added to the manual, if you didn't already. Thanks, Karl

Re: debugging feature for recursive rules

2009-04-14 Thread Ralf Wildenhues
Hi Karl, thanks for the report. * Karl Berry wrote on Sat, Apr 11, 2009 at 02:54:16AM CEST: > I have found myself needing to go through the complicated shell > sequence for the $(RECURSIVE_TARGETS) rule more than once when debugging > the Makefile.am's in a big directory tree (namely TeX Live).

debugging feature for recursive rules

2009-04-10 Thread Karl Berry
I have found myself needing to go through the complicated shell sequence for the $(RECURSIVE_TARGETS) rule more than once when debugging the Makefile.am's in a big directory tree (namely TeX Live). Typically I get a mysterious "*** failed", exit status 1, and there's no easy way to know which comm