Re: -include filename does not show correct dependency errors

[Philip Guenther]

On Wed, Jan 28, 2009 at 9:39 AM, willard <address@hidden> wrote:
> it's the same if foo.d is not a direct target. It's even worse as make fails
> without ANY error message.

Nice!  xxx.h gets marked as failed and the error silenced, and the
silencing applies to all paths to xxx.h and not just the foo.d->xxx.h
path.


> See that the 'make -f bad2.mak' shows no message at all..(but going thru a
> makefile shows Error 2).

("echo $?" after running make works too)


> I am sure I can find a work-around, but this seems like a nasty bug THAT
> SHOULD BE FIXED.

Whoa, no need to yell!  I didn't intend to suggest that the bug should
not be fixed.  My "don't spend time banging you head" comment was for
you, as a user of make, and not the developers of make (of which I am
_not_ one).

Hmm, since you feel strongly about this, the GNU make developers would
probably find it helpful if you were to verify whether this bug still
exists in the development (CVS) version of GNU make and, if so, file a
bug for it or, if there already is bug for it, comment on that bug.
If nothing else, that would let you be notified when the bug *is*
fixed.


Philip Guenther