Follow-up Comment #24, bug #48643 (project make):
If we decide to do this I'm not sure it should be a command line flag: command
line flags should be limited to modifying how a given user wants their build
to run. It shouldn't modify fundamental ways that a makefile is parsed.
The author of the makefile should set some value in the makefile itself, if
they want to modify the way in which rules are searched or applied, because
that's a requirement of the makefile.
Of course that's the problem with backward-incompat: it needs to be an option
so users with newer versions of GNU make can use older makefiles that haven't
been updated. I guess we could allow MAKEFLAGS += --backward-compat to set
it. For sure we'd need to add a new .FEATURE value for this.
What I'd really like to see is a cross-section of builds for popular free
software packages that have this warning enabled to see how many times it's
actually hit. Obviously that's not definitive but it would be useful to know.
I have a setup that builds a bunch of things, maybe I'll try it.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?48643>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
