bug-make
[Top][All Lists]
Advanced

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

Order of variable definition and rule matters!?


From: Jens Schmidt
Subject: Order of variable definition and rule matters!?
Date: 30 Jan 2001 14:31:09 +0100

Hi.

See below for a problem log.

I cannot believe that this is a bug because it seems so basic.
And other makes behave identical.  However, I didn't found a
single line of docu on that in the online-docu (I would have
expected it, or at least a link to it, in section "Using
Variables", subsection "References" or "Flavors".)

Maybe its just my strange way of thinking.  I thought that if it
is the same for recursively expanded variables to write
  FOO = $(BAZ)
  BAZ = baz
or
  BAZ = baz
  FOO = $(BAZ)
then this would apply to the order of variable definition and
rule, too.  Apparently, it does not.  See below.


Regards

Jens


Makefile1:
----------
FOO = foo
baz: $(FOO); @echo $(FOO):$^

Makefile2:
----------
baz: $(FOO); @echo $(FOO):$^
FOO = foo


> touch foo

baz depends on foo in Makefile1:

> gmake -f Makefile1
foo:foo

baz does *not* depend on foo in Makefile2:

> gmake -f Makefile2
foo:
> gmake --version
GNU Make version 3.78.1, by Richard Stallman and Roland McGrath.
Built for Windows32
Copyright (C) 1988, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99
        Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.

Report bugs to <address@hidden>.




reply via email to

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