Follow-up Comment #1, bug #50300 (project make):
I am having this same problem. I am developing a POSIX compliant compiler
which accepts the options requested by POSIX and this behaviour is broken my
makefiles since the compiler follows the utility conventions syntax -O n.
[1] http://pubs.opengro
Follow-up Comment #6, bug #42125 (project make):
I think maybe the naming is unfortunately confusing. A static pattern rule is
best regarded as a form of shorthand. I think many folks read the semantics of
search into the word "pattern", when in this case it's just substitution.
I'd be much more
Follow-up Comment #5, bug #42125 (project make):
I understand why you may consider it counterintuitive based on the naming, but
I don't understand why you consider it unfortunate.
Suppose that we made the change in the implementation that you suggest: that
would mean that the targets listed in th
Follow-up Comment #4, bug #42125 (project make):
(I hope this comment doesn't contribute to an unwanted design discussion.)
Regarding comment #1: _A static pattern rule is a form of explicit rule, not
an implicit rule such as pattern rule._ - While saying that a _static pattern
rule_ is not a _pat
