[bug #45728] .VARIABLES not updated after undefine

2016-03-14 Thread Paul D. Smith
Follow-up Comment #4, bug #45728 (project make): Typo. I fixed it last night in my local repo but haven't pushed that yet. It shouldn't matter. ___ Reply to this item at:

[bug #45728] .VARIABLES not updated after undefine

2016-03-14 Thread Andreas Schwab
Follow-up Comment #3, bug #45728 (project make): Why do the two variables have different types? +static unsigned int variable_changenum; + static unsigned long last_changenum = 0; ___ Reply to this item at:

[bug #45728] .VARIABLES not updated after undefine

2016-03-13 Thread Paul D. Smith
Update of bug #45728 (project make): Status:None => Fixed Assigned to:None => psmith Open/Closed:Open => Closed Fixed Release:

[bug #45728] .VARIABLES not updated after undefine

2015-09-28 Thread anonymous
Follow-up Comment #1, bug #45728 (project make): I think the problem is a bit larger than what is exhibited here. I started with the following script: #!/bin/bash # gmake --version; exec gmake --warn-undefined-variables -f "$0" "$@" MY_foo:=foo undefine MY_foo MY_bar:=bar $(warning MY

[bug #45728] .VARIABLES not updated after undefine

2015-09-03 Thread Andreas Schwab
Additional Item Attachment, bug #45728 (project make): File name: 0001-SV-45728-Force-recomputing-.VARIABLES-when-a-variabl.patch Size:2 KB ___ Reply to this item at:

[bug #45728] .VARIABLES not updated after undefine

2015-08-10 Thread Andreas Schwab
URL: http://savannah.gnu.org/bugs/?45728 Summary: .VARIABLES not updated after undefine Project: make Submitted by: schwab Submitted on: Mo 10 Aug 2015 15:23:58 CEST Severity: 3 - Normal Item Group: Bug

.VARIABLES not updated after undefine

2015-07-14 Thread Andreas Schwab
This makefile demonstrates a bug in the expansion of .VARIABLES: $ cat Makefile.variables MY_one := 1 MY_two := 2 $(foreach v, $(filter MY_%, $(.VARIABLES)), $(eval undefine $v)) MY_foo := foo MY_bar := bar all: @echo MY Variables = $(filter MY_%, $(.VARIABLES)) $ make -f