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: Thu, 28 Mar 2002 09:17:44 +0100	[thread overview]
Message-ID: <200203280817.g2S8HiU22506@cbe.ericsson.se> (raw)


> Delivered-To: 9fans@cse.psu.edu
> To: 9fans@cse.psu.edu
> Subject: Re: [9fans] mk surprises me
> From: forsyth@caldo.demon.co.uk


> >>% : hdr.h
> 
> i suspect that because you've said that everything depends on hdr.h, including 
f2.c,
> it decides it had better remake that too, since hdr.h has changed, but doesn't 
know how.

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).
or, is there a difference between plan9 mk and inferno mk for host systems?

> try using & for this (similar to % but doesn't match . or /)
> 
> &: hdr.h
> 
> &: &.c
> 	cp $stem.c $target

thank you, & works as expected. unfortunatly i am not actually doing
anything with mk, just trying to figure out the documentation (which
uses % in this case).


bengt



             reply	other threads:[~2002-03-28  8:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-28  8:17 Bengt Kleberg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-02  7:49 Bengt Kleberg
2002-03-28 14:52 David Gordon Hogan
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=200203280817.g2S8HiU22506@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).