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: Thu, 19 Dec 2013 09:16:28 +0100 [thread overview]
Message-ID: <CAJUT6o7hmcdmiYK4w3QxNjKi3=cjaRkq5x4XJioghZM0BhQ_Tg@mail.gmail.com> (raw)
In-Reply-To: <CABwHSOtY9_BqJZz-S-PD-Qy3fA5DmOKaOfz1hXBvnCh0MGTC4A@mail.gmail.com>
the problem is not solved, merely one of the manifestation is eliminated.
actual solution requires stating all the dependencies.
if your list of sources and/or targets is dynamic, consider using mk include:
<| GEN_DEPS
where `GEN_DEPS' is your script generating deps in form TARGET: PREREQUISITE
On Wed, Dec 18, 2013 at 10:14 PM, Blake McBride <blake@mcbride.name> wrote:
> Thanks. That is what I was wondering. In the interim, and having a better
> understanding of what is going on, I was able to re-work my mkfile to
> support parallel builds where possible. I am, however, experiencing a new
> problem. I will write that up in a separate post.
>
> Thank for the info!
>
> Blake
>
>
>
> On Wed, Dec 18, 2013 at 3:04 PM, Jacob Todd <jaketodd422@gmail.com> wrote:
>>
>> You could put NPROC=1 in the mkfile.
>
>
next prev parent reply other threads:[~2013-12-19 8:16 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
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 [this message]
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='CAJUT6o7hmcdmiYK4w3QxNjKi3=cjaRkq5x4XJioghZM0BhQ_Tg@mail.gmail.com' \
--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).