>>> I don't follow, that was the point of my patch - ensuring you
>>> get the full path of the offending Makefile rather than an
>>> anonymous "Makefile".
>
>>I though you want to toss the absolute path and use just 'Makefile'
>>instead.
>
>No, that's what we have now - and makes it impossible to locate the offending
>Makefile.

sort of...yeah.  did you give any thought to collapsing stuff like

   /usr/src/foo/bar/fork/knife/spoon/../../../Makefile

to 

   /usr/Makefile

or thereabouts (just as an example)?  what about a "verbose" output
mode that shows that some Makefile included that Makefile.inc which
included that Makefile.inc which included that thing over there which
included that thing which included the thing that had the problem?
kinda like gcc and warnings/errors.

just a thought...

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
andrew@crossbar.com       * "information is power -- share the wealth."