Hi Kai,
I think it would be useful, but in a slightly different way. The
information printed during make can be informative, but too much of the
output is just redundant. I'd prefer a change something like the
following:
--- ../gold-2.5/Rules.make Fri May 31 22:10:04 2002
+++ ./Rules.make Fri May 31 22:56:33 2002
@@ -399,5 +399,5 @@
if_changed = $(if $(strip $? \
$(filter-out $($(1)),$(cmd_$(@F)))\
$(filter-out $(cmd_$(@F)),$($(1)))),\
- @echo '$($(1))' && $($(1)) && echo 'cmd_$@ := $($(1))' > $(@D)/.$(@F).cmd)
+ @echo '$(subst $(CFLAGS),$$CFLAGS,$(strip $($(1))))' && $($(1)) && echo 'cmd_$@ := $($(1))' > $(@D)/.$(@F).cmd)
which causes output to look like:
gcc $CFLAGS -DKBUILD_BASENAME=raw -c -o raw.o raw.c
gcc $CFLAGS -DKBUILD_BASENAME=pty -DEXPORT_SYMTAB -c -o pty.o pty.c
gcc $CFLAGS -DKBUILD_BASENAME=misc -DEXPORT_SYMTAB -c -o misc.o misc.c
gcc $CFLAGS -DKBUILD_BASENAME=random -DEXPORT_SYMTAB -c -o random.o random.c
gcc $CFLAGS -DKBUILD_BASENAME=vt -c -o vt.o vt.c
gcc $CFLAGS -DKBUILD_BASENAME=vc_screen -c -o vc_screen.o vc_screen.c
IMO, this has all the advantages of the "quiet" output, but none of the
information loss. (The only thing suppressed is CFLAGS which doesn't
change.)
-Kevin
-- ------------------------------------------------------------------------ | Kevin O'Connor "BTW, IMHO we need a FAQ for | | kevin@koconnor.net 'IMHO', 'FAQ', 'BTW', etc. !" | ------------------------------------------------------------------------ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/