Follow-up Comment #3, bug #66030 (group make): I think we are just disagreeing over a matter of technical semantics.
Make is showing the target it is currently considering, and which it
determined to be out of date and so forced make to run the recipe. In your
example, that target is "foo.h". The fact that "foo.c" is _also_ updated by
this recipe is not relevant to make, at least not at this time.
I am not saying that the trace messaging should not be enhanced, or that make
doesn't know this information. All I'm saying is that the above is why make
shows that target (and only that target): that's the target that was
discovered to be out of date and that's what make is showing here. It is not
showing what targets it thinks the recipe will generate, although obviously in
most cases these are the same thing.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66030>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
