From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <20131218164042.524C6B827@mail.bitblocks.com> References: <20131218164042.524C6B827@mail.bitblocks.com> Date: Wed, 18 Dec 2013 11:28:21 -0600 Message-ID: From: Blake McBride To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=047d7bdc119a186c1304edd25f65 Subject: Re: [9fans] Problem with mk Topicbox-Message-UUID: 9fd2311c-ead8-11e9-9d60-3106f5b1d025 --047d7bdc119a186c1304edd25f65 Content-Type: text/plain; charset=ISO-8859-1 Often there is a set of reasonable, alternative algorithms one may utilize to solve a problem. Then, there is a set of unreasonable algorithms one may employ that may or may not solve the problem given various conditions. "make" has a proven reasonable algorithm to solve the problem for which it was designed. It employs one algorithm among other possible, and equally good, algorithms. You are implying that mk is using another valid algorithm rather than an unreasonable one. I can't see it yet. I'd be a better judge if I understood the purposeful, thought out reason behind the problems I am experiencing - assuming there is one. "That's just the way it works" or "we do it differently because we are not unix" are stupid as hell arguments. I remain confident that there is a thought out, reasonable algorithm employed by mk that I am yet ignorant of. Blake On Wed, Dec 18, 2013 at 10:40 AM, Bakul Shah wrote: > On Wed, 18 Dec 2013 10:11:22 CST Blake McBride 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. > > --047d7bdc119a186c1304edd25f65 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Often there is a set of reasonable, alternative algorithms= one may utilize to solve a problem. =A0Then, there is a set of unreasonabl= e algorithms one may employ that may or may not solve the problem given var= ious conditions. =A0"make" has a proven reasonable a= lgorithm to solve the problem for which it was designed. =A0It employs one = algorithm among other possible, and equally good, algorithms. =A0You are im= plying that mk is using another valid algorithm rather than an= unreasonable one. =A0I can't see it yet.

I'd be a better judge if I understood the purposeful, th= ought out reason behind the problems I am experiencing - assuming there is = one. =A0"That's just the way it works" or "we do it diff= erently because we are not unix" are stupid as hell arguments.

I remain confident that there is a thought out, reasona= ble algorithm employed by mk that I am yet ignorant of.
<= div>
Blake


On Wed, Dec 18, 2013 at 10:40 AM, Bakul Shah &= lt;bakul@bitblocks= .com> wrote:
On Wed, 18 Dec 2013 10:11:= 22 CST Blake McBride <blake@mcbrid= e.name> wrote:
> >
> > Somehow Unix or GNU "make" doesn't mix up buffered = stdout with unbuffered
> > stderr output. =A0They remain in order so the total = out of make and all of
> > the commands are shown in order and in context. =A0Y= ou know, so a human can
> > understand it. =A0mk appears not to han= dle this the same. =A0stdout output
> > and stderr output are tota= lly 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 <= span id=3D"60b53753-4451-4277-9e59-3dad30668d95" class=3D"GINGER_SOFTWARE_m= ark">expect
it to behave like make, it pays to understand how mk works,
may be by experimenting with little mkfiles.


--047d7bdc119a186c1304edd25f65--