[bug #45311] makes only one of two dependencies that depend on the same subdir-pattern rule

2015-07-11 Thread Paul D. Smith
Follow-up Comment #5, bug #45311 (project make): We'd have to ask Roland or RMS; that behavior was already present when I first started using GNU make, IIRC, and I'm not sure where it originated. I think the idea that you can generate multiple outputs with a single command is a very important

[bug #45311] makes only one of two dependencies that depend on the same subdir-pattern rule

2015-06-13 Thread Frank Heckenbach
Follow-up Comment #4, bug #45311 (project make): $@ wasn't the source of my confusion. Though the simplified test case would indeed have worked if $@ expanded to all targets, my actual Makefile wouldn't. What confused me was the different behaviour of multiple-target rules with and without

[bug #45311] makes only one of two dependencies that depend on the same subdir-pattern rule

2015-06-12 Thread Frank Heckenbach
URL: http://savannah.gnu.org/bugs/?45311 Summary: makes only one of two dependencies that depend on the same subdir-pattern rule Project: make Submitted by: frank Submitted on: Fr 12 Jun 2015 22:55:52 GMT Severity: 3 -

[bug #45311] makes only one of two dependencies that depend on the same subdir-pattern rule

2015-06-12 Thread Paul D. Smith
Follow-up Comment #3, bug #45311 (project make): Well, make walks targets one at a time, so there will always be a first target which is determined to be out of date and matches a given pattern rule, causing the recipe to fire. That target is the one that will be set with $@. The rest of the

[bug #45311] makes only one of two dependencies that depend on the same subdir-pattern rule

2015-06-12 Thread Paul D. Smith
Update of bug #45311 (project make): Status:None = Not A Bug Open/Closed:Open = Closed ___ Follow-up Comment #1: I may be missing

[bug #45311] makes only one of two dependencies that depend on the same subdir-pattern rule

2015-06-12 Thread David Boyce
Follow-up Comment #2, bug #45311 (project make): I think the confusion here has to do with the value of $@. One might reasonably expect, in a multi-target pattern rule, that $@ would be the list of all matching out-of-date targets but in fact, according to the documentation: In a pattern rule