From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] mk surprises me
Date: Wed, 27 Mar 2002 14:40:45 +0100 [thread overview]
Message-ID: <200203271340.g2RDekt13862@copernicus.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Wed, 27 Mar 2002 14:10:52 +0100." <200203271310.g2RDAqU02875@cbe.ericsson.se>
Someone more knowledgeable will surely correct me, if needed.
Don't you need to include one of the general mk 'rule templates'
(mkone, mkmany or such)? At least, that's what I recall seeing in
the plan 9 source tree, and in a similar way in the drawterm source.
Axel.
> mk does not do what i expect it to do. here are some facts:
>
>
> the mkfile
>
> % : hdr.h
>
> % : %.c
> cp $stem.c $target
>
>
> the files
> -rw-rw-r-- 1 eleberg avall 0 Mar 20 15:47 f2.c
> -rw-rw-r-- 1 eleberg avall 0 Mar 27 13:12 f2
> -rw-rw-r-- 1 eleberg avall 0 Mar 27 13:17 hdr.h
>
>
> the test
> ; inferno/Solaris/sparc/bin/mk -f mkfile f2
> mk: no recipe to make 'f2.c'
>
>
> according to my interpretation of 'maintaining files on plan9 with mk'
> (from plan9v2 documentation), page 188, the mkfile should produce f2
> from f2.c if hdr.h is younger then f2. but instead i get the error
> message above that i do not understand.
> is there anybody that sees where i go wrong?
>
> possible sources of errors:
> i use mk from inferno, not plan9
> i have only the plan9v2 documentation, not v3 documentation.
> i am not very good with mkfiles
>
>
> bengt
>
next prev parent reply other threads:[~2002-03-27 13:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-27 13:10 Bengt Kleberg
2002-03-27 13:40 ` Axel Belinfante [this message]
2002-03-27 13:56 ` Axel Belinfante
2002-03-27 14:10 forsyth
2002-03-28 8:01 Bengt Kleberg
2002-03-28 10:50 ` Axel Belinfante
2002-03-28 11:04 ` William Josephson
2002-03-28 8:17 Bengt Kleberg
2002-03-28 14:52 David Gordon Hogan
2002-04-02 7:49 Bengt Kleberg
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=200203271340.g2RDekt13862@copernicus.cs.utwente.nl \
--to=axel.belinfante@cs.utwente.nl \
--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).