From: Bakul Shah <bakul@bitblocks.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 08:40:42 -0800 [thread overview]
Message-ID: <20131218164042.524C6B827@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Wed, 18 Dec 2013 10:11:22 CST." <CABwHSOuJ9thp9xhHYVK+0OM1_k9WRUCipxFqUdETJHcm8KAEXg@mail.gmail.com>
On Wed, 18 Dec 2013 10:11:22 CST Blake McBride <blake@mcbride.name> wrote:
> >
> > Somehow Unix or GNU "make" doesn't mix up buffered stdout with unbuffered
> > stderr output. They remain in order so the total out of make and all of
> > the commands are shown in order and in context. You know, so a human can
> > understand it. mk appears not to handle this the same. stdout output
> > and stderr output are totally out of sequence making it very, very
> > difficult to understand what is going on.
> >
> >
> mk should flush stdout after completion each command.
Just as plan9 is not unix, mk is not make. Rather than expect
it to behave like make, it pays to understand how mk works,
may be by experimenting with little mkfiles.
next prev parent reply other threads:[~2013-12-18 16:40 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
2013-12-19 16:20 ` Blake McBride
2013-12-18 16:11 ` Blake McBride
2013-12-18 16:40 ` Bakul Shah [this message]
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=20131218164042.524C6B827@mail.bitblocks.com \
--to=bakul@bitblocks.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).