Path: utzoo!mnetor!uunet!husc6!mit-eddie!bbn!rochester!PT.CS.CMU.EDU!K.GP.CS.CMU.EDU!bww
From: bww@K.GP.CS.CMU.EDU (Bradley White)
Newsgroups: comp.bugs.4bsd
Subject: Re: Bug in the make program (?!)
Message-ID: <1048@PT.CS.CMU.EDU>
Date: 5 Mar 88 22:41:12 GMT
References: <110@cui.UUCP>
Sender: netnews@PT.CS.CMU.EDU
Organization: Carnegie-Mellon University, CS/RI
Lines: 15
Summary: make -n != make

In article <110@cui.UUCP>, dimitri@cui.UUCP (KONSTANTAS Dimitri) writes:
> Using the make program, I came to case where make behaves differently
> when executed with the -n option and without.

It should not be surprising that "make" and "make -n" can do different
things.  "make -n" assumes that an "a: b c" rule actually makes "a" out
of "b" and "c", and that it does it ``now'', whereas "make" can stat()
"a" after the commands are run to see if it was really made.  In
general, rules that don't make their targets (like those given), or
rules that try to be smart about making their target even though the
dependencies are out of date (for example, trying to detect benign
changes), will always confuse "make -n".
-- 
Bradley White <bww@cs.cmu.edu>         +1-412-268-3060
CMU Computer Science Department  40 26'33"N 79 56'48"W