[bug #63439] [Regression] --no-builtin-variables with --warn-undefined-variables trigger warning on GNUMAKEFLAGS

2022-11-30 Thread malcolm cook
Follow-up Comment #2, bug #63439 (project make): FWIW: The exact same issue is present for the variable MAKECMDGOALS. I have reported it as #63452 ___ Reply to this item at:

[bug #63452] [Regression] --no-builtin-variables with --warn-undefined-variables trigger warning on MAKECMDGOALS

2022-11-30 Thread malcolm cook
URL: Summary: [Regression] --no-builtin-variables with --warn-undefined-variables trigger warning on MAKECMDGOALS Project: make Submitter: malcook Submitted: Wed 30 Nov 2022 06:42:05 PM UTC

[bug #63439] [Regression] --no-builtin-variables with --warn-undefined-variables trigger warning on GNUMAKEFLAGS

2022-11-30 Thread Paul D. Smith
Follow-up Comment #3, bug #63439 (project make): It's true that the same issue exists for this, but in this case it's not a regression. It also warned in previous releases: ~$ make --version GNU Make 4.3 ~$ echo 'all:;echo $(GNUMAKEFLAGS)' | make -f- --warn-undefined-variables echo ~$ echo

[bug #63439] [Regression] --no-builtin-variables with --warn-undefined-variables trigger warning on GNUMAKEFLAGS

2022-11-30 Thread malcolm cook
Follow-up Comment #4, bug #63439 (project make): I perhaps was over-eager to chalk up my observation as being the same underlying issue. I still think there is a regression, but I certainly misreported it. Try this: /tmp$ make -f- <<<$'MAKEFLAGS += --warn-undefined-variables \n $(info