From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <200204020749.g327n6U27342@cbe.ericsson.se> From: Bengt Kleberg Subject: Re: [9fans] mk surprises me To: 9fans@cse.psu.edu MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Date: Tue, 2 Apr 2002 09:49:06 +0200 Topicbox-Message-UUID: 71587bb0-eaca-11e9-9e20-41e7f4b1d025 > Delivered-To: 9fans@cse.psu.edu > To: 9fans@cse.psu.edu > Subject: Re: [9fans] mk surprises me > From: David Gordon Hogan > > the behaviour i expect (cp f1.c f1, even when f1.c was older than f1, > > provided that hdr.h was younger than f1) is the one described in > > plan9v2 documentation. admitedly your suspicion sounds much more > > logical than the documenation. > > i have (as well as i can) copied the contents of the mkfile from the book. > > perhaps this is an error in the book? (there are others). > > I can not find your example in the documentation. Could you > please provide a reference? (Name of paper and section name, > please). Plan9, The Documents. Maintaining Files on Plan9 with Mk. page 191. This is Plan9 v2 (with Inferno around, making it possible to avoid C, I never bought Plan9 v3). ...deleted > Charles' diagnonis of the problem is correct, that > you have effectively made f1.c depend on hdr.h, but not provided > a recipe for making f1.c, hence if hdr.h is more recent than > f1.c, mk complains. The solution is to change the rule so that the > source file f1.c doesn't depend on hdr.h. > this is fine. thank you. bengt