[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #36844] Private variables can still leak to dependencies if += is u

From: Brian Vandenberg
Subject: [bug #36844] Private variables can still leak to dependencies if += is used
Date: Fri, 13 Jul 2012 18:28:40 +0000
User-agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Win64; x64; Trident/4.0; .NET CLR 2.0.50727; SLCC2; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E)

Follow-up Comment #1, bug #36844 (project make):

In the original submission, I left out a couple of lines in the section
exemplifying the problem; the variables 'T1' and 'T2' are there strictly for
the sake of making it convenient to test this without having to modify the
makefile for each test.

It should've read as follows:

To test this: 

# Comment out lines 3 & 6-11; this will demonstrate how private variables
should behave 
gmake T1='#' T2='#' 
C: global 
B: global 
A: global A1 A2 
# Comment out just line 3; this will demonstrate the problem; targets B & C
inherit changes from things that depend on them. 
gmake T2='#'
C: global A1 A2 B1 B2 C1 C2 
B: global A1 A2 B1 B2 
A: global A1 A2 
# Don't comment out any lines; adding a pattern rule to wipe out ASDF for all
targets is a reasonable work-around until this problem gets fixed: 
C: global C1 C2 
B: global B1 B2 
A: global A1 A2


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]