Re: Plan for better error reporting, tracing, debugging in GNU make (1st steps)

[Henning Makholm]

Scripsit R. Bernstein

> Ditto for info that front ends which might call "make" could
> better use and how to best serve them in parsing the errors. For
> example, should I try to put in the full path in error line? (It seems
> that most of the files are called "Makefile", it just the directory
> that keeps changing.)

Emacs, at least, is able to keep track of the working directory by
recognizing "entering/leaving directory foo" messages from recursive
make instances, so this should not be a problem.

It can probably safely be assumed that all serious tools that try to
parse make output will know to do something like that; otherwise
compiler error messages (which usually give only relative file names)
will be difficult to match to actual source files in a deep tree.

-- 
Henning Makholm         "Vend dig ikke om! Det er et meget ubehageligt syn!"