[bug #9060] --warn-undefined-variables

Follow-up Comment #7, bug #9060 (project make): Thank you! I shall look forward to this great improvement in the next release! ___ Reply to this item at: ___

[bug #9060] --warn-undefined-variables

Update of bug #9060 (project make): Status:None => Fixed Open/Closed:Open => Closed Fixed Release:None => SCM __

[bug #9060] --warn-undefined-variables

Follow-up Comment #5, bug #9060 (project make): Echoing past comments, this is both a very useful feature to have and currently a confusing behavior. ___ Reply to this item at:

[bug #9060] --warn-undefined-variables

Follow-up Comment #4, bug #9060 (project make): The way make currently works is that MAKEFLAGS is re-parsed only after all the makefiles have been read in and before make is about to start running recipes. MAKEFLAGS is not reparsed immediately every time it's changes. This leads to the behavior

[bug #9060] --warn-undefined-variables

Follow-up Comment #3, bug #9060 (project make): Specifying MAKEFLAGS += --warn-undefined-variables within a Makefile is not equivalent to specifying the same option on the command-line. Test case: MAKEFLAGS += --warn-undefined-variables $(foo): @echo foo bar: @echo $(bar) This b

[bug #9060] --warn-undefined-variables

Follow-up Comment #2, bug #9060 (project make): Apparently you can turn this on in a Makefile with MAKEFLAGS += --warn-undefined-variables I'm using 3.81 and this works from an included makefile before any variable references. ___ Reply t

[bug #9060] --warn-undefined-variables

Follow-up Comment #1, bug #9060 (project make): Yes, please. Personally, I believe it was a great misfeature of the original make that it quietly uses undefined variables without warning. For those of us supporting other users who are bad typists or bad proofreaders, please provide us a mechani