This is the mail archive of the
automake@gnu.org
mailing list for the automake project.
Re: make variables defined via include
- From: Alexandre Duret-Lutz <duret_g at lrde dot epita dot fr>
- To: Harlan Stenn <Harlan dot Stenn at pfcs dot com>
- Cc: automake at gnu dot org
- Date: Tue, 21 May 2002 09:56:50 +0200
- Subject: Re: make variables defined via include
- References: <45511.1021700236@dog.pfcs.com>
>>> "Harlan" == Harlan Stenn <Harlan.Stenn@pfcs.com> writes:
[...]
Harlan> Unfortunately, it now appears that at the time when the
Harlan> Makefile is initially scanned (by gmake 1.79.1),
Harlan> $(libfoo_la_LIBDEP) is not defined, so it does not
Harlan> appear as a dependency. However, when "make" goes to
Harlan> create the target, $(libfoo_la_LIBDEP) *is* defined, so
Harlan> the link fails because the library has not yet been
Harlan> built.
Harlan> Is this making sense?
Sounds like you just hit the declaration-order-does-matter issue:
http://gcc.gnu.org/ml/gcc-patches/2001-05/msg01692.html
Harlan> Any ideas on how to fix the problem?
Define your rules only once all involved variables are defined?
--
Alexandre Duret-Lutz