On Tue, 2012-04-03 at 16:20 -0600, Teng wrote:
> Excuse me. I have a question about Section 3.7 of the GNU Make Manual
> Version 3.81 whose title is "How Makefiles Are Remade". It said
> "After reading in all mkefiles, make will consider each as a goal target
> and attempt to update it." But accord
Hello, the author of the GNU Make Manual.
Excuse me. I have a question about Section 3.7 of the GNU Make Manual
Version 3.81 whose title is "How Makefiles Are Remade". It said
"After reading in all mkefiles, make will consider each as a goal target
and attempt to update it." But according to my ex
Paul,
Thank you for the prompt pointer to this information.
I have been experimenting with the private & export keywords, but still I
encounter an odd behavior related to the ordering of two rules with
target-specific variables and a single shared prerequisite. For example, the
example below
On Mon, 2012-04-02 at 23:13 -0400, Brown, Ruben wrote:
> Is this behavior by design or an unfortunately long lived bug? If it
> is by design, what purpose does maintaining this behavior serve?
>
> ***Makefile***
> .PHONY: all A B
> all: A
> VAR := 0
> A: B
> A: VAR:= 1
> B:
> @echo VAR=$(VAR
I have a question about a behavior I'm seeing in gnu make 3.82. The behavior
seems undesirable, but has persisted from at least as far back as 3.79. The
behavior can be demonstrated with a very simple make file with two targets, A
and B and a single variable VAR. I have included an example below
