9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bengt Kleberg <eleberg@cbe.ericsson.se>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] mk surprises me
Date: Tue,  2 Apr 2002 09:49:06 +0200	[thread overview]
Message-ID: <200204020749.g327n6U27342@cbe.ericsson.se> (raw)


> Delivered-To: 9fans@cse.psu.edu
> To: 9fans@cse.psu.edu
> Subject: Re: [9fans] mk surprises me
> From: David Gordon Hogan <dhog@plan9.bell-labs.com>


> > 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



             reply	other threads:[~2002-04-02  7:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-02  7:49 Bengt Kleberg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-28 14:52 David Gordon Hogan
2002-03-28  8:17 Bengt Kleberg
2002-03-28  8:01 Bengt Kleberg
2002-03-28 10:50 ` Axel Belinfante
2002-03-28 11:04   ` William Josephson
2002-03-27 14:10 forsyth
2002-03-27 13:10 Bengt Kleberg
2002-03-27 13:40 ` Axel Belinfante
2002-03-27 13:56   ` Axel Belinfante

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200204020749.g327n6U27342@cbe.ericsson.se \
    --to=eleberg@cbe.ericsson.se \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).