Bug #78441 for makepp: target specific variables evaluated incorrectly

Tue Jul 17 22:34:49 2012 yshtil [...] nvidia.com - Ticket created

CC:	Sergei Skokov <sskokov [...] nvidia.com>
Subject:	target specific variables evaluated incorrectly
Date:	Tue, 17 Jul 2012 19:34:37 -0700
To:	"bug-makepp [...] rt.cpan.org" <bug-makepp [...] rt.cpan.org>
From:	Yuri Shtil <yshtil [...] nvidia.com>

Hi, When the following code runs via gnu make and makepp-2.0 the results are different: # command 'makepp a' # gives MYVAR which has target specific EXTRA_VAL but misses VAL a : MYVAR += EXTRA_VAL MYVAR += VAL ifdef MAKE_VERSION a : else $(phony a): endif @echo MYVAR=$(MYVAR) ----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. -----------------------------------------------------------------------------------

Thu Jul 19 16:16:14 2012 occitan [...] esperanto.org - Taken

Thu Jul 19 16:21:01 2012 occitan [...] esperanto.org - Correspondence added

Hi Yuri, well spotted – gmake is full of surprises. I would at least have expected the words to come out the other way round, since the specific appending is seen first... I'm undecided whether such a border case merits a major rework of mpp's assignment handling. Anyway the short term solution would be to put the general assignment above the other one. regards -- Daniel

Thu Jul 19 16:21:02 2012 The RT System itself - Status changed from 'new' to 'open'