bugmake - Bugs: bug #43363, Variable is broken after $(eval)...

 
 

bug #43363: Variable is broken after $(eval) within recipe

Submitter:  Konstantin Demin <rockdrilla>
Submitted:  Mon 06 Oct 2014 06:49:39 AM UTC
   
 
Severity:  3 - Normal Item Group:  Bug
Status:  None Privacy:  Public
Assigned to:  None Open/Closed:  Open
Component Version:  4.0 Operating System:  POSIX-Based
Fixed Release:  None Triage Status:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Sun 12 Jul 2015 09:41:33 PM UTC, comment #1: 

It's fantastic that you've provided reproducible cases (although please attach the sample files directly to the bug in the future rather than using pastebin).

However for errors this complex it would be really, really helpful if for each example you could point to exactly which part of the output you felt was incorrect and what you think the correct output should be... without that information it takes a lot of effort to examine every line and determine whether it makes sense or not.

Paul D. Smith <psmith>
Group administrator
Mon 06 Oct 2014 06:49:39 AM UTC, original submission:  

I'm trying to implement prerequisite feedback via environment backpropagation.

Here's "test.1":
( http://pastebin.com/ZiEJpEhr )
--- [ test.1 ] ---
::  T=a b c d e
::  .PHONY: $(T)
::  $(T):
::  $(if $($(@)_BRINGBACK),$(eval $($(@)_BRINGBACK)))
::  $(if $($(@)_BRINGBACK),@echo '>' $@':' $(@)_BRINGBACK = $($(@)_BRINGBACK))
::  $(if $(LDFLAGS),@echo '>' $@':' LDFLAGS = $(LDFLAGS))
:: @echo '>' $@':'$(if $+, $+)$(if $|, '|' $|)
::
::  .DEFAULT: a
::  a: b | c
::  b: d
::  c: e
::  e_BRINGBACK = LDFLAGS += -lz
--- [ test.1 ] ---

--- [ test.1 output ] ---
::  d:
::  b: d
::  e: e_BRINGBACK = LDFLAGS += -lz
::  e: LDFLAGS = -lz
::  e:
::  c: LDFLAGS = -lz
::  c: e
::  a: LDFLAGS = -lz
::  a: b | c
--- [ test.1 output ] ---

Append global environment variable to "test.1" and name it "test.2":
( http://pastebin.com/JqUN36ZP )
--- [ test.2 ] ---
::  LDFLAGS = -lm
--- [ test.2 ] ---

--- [ test.2 output ] ---
::  d: LDFLAGS = -lm
::  d:
::  b: LDFLAGS = -lm
::  b: d
::  e: e_BRINGBACK = LDFLAGS += -lz
::  e: LDFLAGS = -lm -lz
::  e:
::  c: LDFLAGS = -lm -lz
::  c: e
::  a: LDFLAGS = -lm -lz
::  a: b | c
--- [ test.2 output ] ---

Append target environment variable to "test.1" and name it "test.3":
( http://pastebin.com/z9L17eaJ )
--- [ test.3 ] ---
::  a: LDFLAGS = -lm
--- [ test.3 ] ---

--- [ test.3 output ] ---
::  d: LDFLAGS = -lm
::  d:
::  b: LDFLAGS = -lm
::  b: d
::  e: e_BRINGBACK = LDFLAGS += -lz
::  e: LDFLAGS = -lm
::  e:
::  c: LDFLAGS = -lm
::  c: e
::  a: LDFLAGS = -lm
::  a: b | c
--- [ test.3 output ] ---

Append slightly different target environment variable to "test.1" and name it "test.4":
( http://pastebin.com/jGaz8H8t )
--- [ test.4 ] ---
::  a: LDFLAGS += -lm
--- [ test.4 ] ---

--- [ test.4 output ] ---
::  d: LDFLAGS = -lm
::  d:
::  b: LDFLAGS = -lm
::  b: d
::  e: e_BRINGBACK = LDFLAGS += -lz
::  e: LDFLAGS = -lm -lz -lm
::  e:
::  c: LDFLAGS = -lm -lz -lm
::  c: e
::  a: LDFLAGS = -lm -lz -lm
::  a: b | c
--- [ test.4 output ] ---

Append target variable and global variable to "test.4" and name it "test.5":
( http://pastebin.com/5hv5jzFq )
--- [ test.5 ] ---
::  LDFLAGS += -lbz2
--- [ test.5 ] ---

--- [ test.5 output ] ---
::  d: LDFLAGS = -lbz2 -lm
::  d:
::  b: LDFLAGS = -lbz2 -lm
::  b: d
::  e: e_BRINGBACK = LDFLAGS += -lz
::  e: LDFLAGS = -lm -lz -lm
::  e:
::  c: LDFLAGS = -lm -lz -lm
::  c: e
::  a: LDFLAGS = -lm -lz -lm
::  a: b | c
--- [ test.5 output ] ---

I've rebuilt make with DEB_BUILD_OPTIONS="nostrip noopt" and debugged with file "test.5".

I've discovered two moments which determine such behavior:
1) appending to variable in "$(eval ...)" takes only first value in chain.

  e.g.:
  LDFLAGS defined in global context as "LDFLAGS += 1" and in target "A" as "LDFLAGS += 2", then actual value for "A" and all it's prerequisites will be "1 2".
  Calling "$(eval LDFLAGS += 3)" in recipe of target "A" or any prerequisite defines "LDFLAGS" as "2 3".

2) variable assignment during "$(eval ...)" in recipe sets new value in top-most variable without setting "variable.recursive = 0".

  i.e.:
  LDFLAGS after "$(eval ...)" equals "2 3" and defined in global context, but it's still recursive, that's why LDFLAGS is equal "2 3 2".

Imho, there're several points to fix:
1) variable manipulations during "$(eval)" in recipe context may be handled in same way as variable assignment in recipes (i.e. "A: LDFLAGS += X");
2) variable assignment during "$(eval)" may grab entire value instead of first non-empty value in chain;
3) variable's flag "recursive" may be set to "0" if value was overwritten.

PS: this bug is reproducible in 3.81 too.

--
SY,
Konstantin Demin

Konstantin Demin <rockdrilla>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by psmith (Posted a comment)
  • -email is unavailable- added by rockdrilla (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    No changes have been made to this item

    Back to the top

    Powered by Savane 3.13-758e.
    Corresponding source code