it's the same if foo.d is not a direct target. It's even worse as make fails without ANY error message. Example2: $ cat bad2.mak
all: foo.ooo COMPILE=gcc %.o: %.c $(COMPILE) -c $< %.d: %.c $(COMPILE) -c $< -MM -o $*.d -include foo.d foo.ooo: foo.o ld -o foo.ooo foo.o [/cygdrive/d/opentv/tstmake] $ make -f bad2.mak [/cygdrive/d/opentv/tstmake] $ cat makefile all: $(MAKE) -f bad2.mak [/cygdrive/d/opentv/tstmake] $ make make -f bad2.mak make: *** [all] Error 2 [/cygdrive/d/opentv/tstmake] $ cat foo.d foo.d foo.o: foo.c xxx.h See that the 'make -f bad2.mak' shows no message at all..(but going thru a makefile shows Error 2). I am sure I can find a work-around, but this seems like a nasty bug THAT SHOULD BE FIXED. -- View this message in context: http://www.nabble.com/-include-filename-does-not-show-correct-dependency-errors-tp21699973p21710735.html Sent from the Gnu - Make - Bugs mailing list archive at Nabble.com. _______________________________________________ Bug-make mailing list Bug-make@gnu.org http://lists.gnu.org/mailman/listinfo/bug-make