Paul,
Paul D. Smith [EMAIL PROTECTED] writes:
I disagree, actually. It's a settled feature of make that the DAG is
not a simple tree: that there can be more than one pathway to a given
target in the DAG.
The placement of the .WAIT prerequisite implies a relationship between
two
Hello,
8.8 The eval Function has an example of using eval, foreach, ... and I am
planning on using something a bit like that myself. The example provided
has a two problems and I have a fixed version
(tested on GNU Make 3.80 on solaris).
You might like to incorporate this fixed version in the
%% James Coleman [EMAIL PROTECTED] writes:
jc Two lines had problems: (see original Makefile and modified one (as in
jc tgz) below)
jc$(1): $$($(1)_OBJ) $$($(1)_LIBS:%=-l%)
jc and
jc $(LINK.o) $^ $(LDLIBS) -o $@
jc The first makes e.g. -lpriv and -lprotocol dependancies
%% Boris Kolpackov [EMAIL PROTECTED] writes:
bk Yes it does. It's not clear to me whether it's good or bad, though.
bk I don't see how result depends on how we got here type of logic
bk is of any usefulness especially in the context of make (read build
bk reproducibility).
bk In this
