From: dexen deVries <dexen.devries@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Problem with mk
Date: Wed, 18 Dec 2013 16:37:51 +0100 [thread overview]
Message-ID: <5446730.4oMZM0t5oA@coil> (raw)
In-Reply-To: <CABwHSOukAs36eJ2zA2Q=yeaN53hWAsm2EPOSZJmkOHkhTwXQBA@mail.gmail.com>
On Wednesday 18 of December 2013 09:23:19 Blake McBride wrote:
>
> Problem 1:
>
it seems you have an un-stated dependency/cies among your intermediate targets
/ prerequisites.
Say, foo.o depends on foo.c and foo.h -- but foo.h also depends on
generated_foo.h, which should be generated by make.
in such case, explicitly state (no recipe is necessary):
foo.h: generated_foo.h
so mk knows the `generated_foo.h' must be completed first.
> Problem 2:
>
> Even though I am executing mk with the "-s" option, it still seems like it
> is running in parallel because a subsequent command can't find a file
> created by a prior command - as if it didn't wait for the prior command to
> finish. Remember this build fine, and without error codes, when executed
> manually.
-s won't help you there, because it regards processing of /command line/
arguments, not of prerequisites. consider:
$ NPROC=1 mk my_target
also investigate -d[egp] debug stuff.
have fun with mk, it's a great little tool :-)
--
dexen deVries
[[[↓][→]]]
Take care of the luxuries and the necessities will take care of themselves.
-- L. Long
next prev parent reply other threads:[~2013-12-18 15:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 15:23 Blake McBride
2013-12-18 15:37 ` dexen deVries [this message]
2013-12-18 16:07 ` Blake McBride
2013-12-18 20:21 ` Blake McBride
2013-12-18 21:04 ` Jacob Todd
2013-12-18 21:14 ` Blake McBride
2013-12-19 8:16 ` dexen deVries
2013-12-19 16:20 ` Blake McBride
2013-12-18 16:11 ` Blake McBride
2013-12-18 16:40 ` Bakul Shah
2013-12-18 17:06 ` Aram Hăvărneanu
2013-12-18 17:18 ` Blake McBride
2013-12-18 17:27 ` Rubén Berenguel
2013-12-18 17:28 ` Blake McBride
2013-12-18 17:47 ` Kurt H Maier
2013-12-18 18:13 ` Bakul Shah
2013-12-18 18:20 ` Blake McBride
2013-12-18 18:28 ` Blake McBride
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=5446730.4oMZM0t5oA@coil \
--to=dexen.devries@gmail.com \
--cc=9fans@9fans.net \
/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).