From: Chet Ramey <chet.ramey@case.edu>
To: John Cowan <cowan@ccil.org>, Steve Nickolas <usotsuki@buric.co>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Style command source available?
Date: Thu, 20 Aug 2020 15:42:39 -0400 [thread overview]
Message-ID: <5c629889-d4b0-761e-9eb2-76b73ffa097b@case.edu> (raw)
In-Reply-To: <CAD2gp_SudcMNYbz-h4RZURG--nWF-KcLoQxEFy6W4tAqpnt=sg@mail.gmail.com>
On 8/20/20 12:08 PM, John Cowan wrote:
>
>
> On Thu, Aug 20, 2020 at 11:55 AM Steve Nickolas <usotsuki@buric.co
> <mailto:usotsuki@buric.co>> wrote:
>
>
> Funny you mention ksh since I've been trying to kitbash ksh93 into being
> able to compile with make instead of the funky build system it currently
> uses, without a lot of luck.
>
>
> IIRC, Korn used make when developing ksh, but then shipped it with a
> /bin/sh script because it was more portable than make was in those days
> (and still is; there are tools that warn you to use gmake on BSD). After
> all, a build process (unless it is interrupted) just needs to build, it
> doesn't need to keep track of what has already been built.
He might have started with make for ksh83 and 86, but switched to Fowler's
nmake and then shipped that /bin/sh script in ksh88 for people (everyone,
basically) who didn't have nmake.
> That said, I have no idea what the state of the build process is now.
Changing that was one of the controversial modifications made to ksh93 in
ksh-2020. It's pretty complex.
Here's a paper that describes part of it:
https://www.usenix.org/legacy/publications/library/proceedings/vhll/full_papers/fowler.feature.ps
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
next prev parent reply other threads:[~2020-08-20 19:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-20 14:09 Richard Salz
2020-08-20 14:45 ` Jim Geist
2020-08-20 15:14 ` Clem Cole
2020-08-20 15:44 ` Steve Nickolas
2020-08-20 16:08 ` John Cowan
2020-08-20 16:30 ` Steve Nickolas
2020-08-20 16:48 ` John Cowan
2020-08-20 19:42 ` Chet Ramey [this message]
2020-08-20 23:15 ` John Cowan
2020-08-20 23:17 ` Chet Ramey
2020-08-20 23:20 ` Jim Capp
2020-08-21 9:21 ` Harald Arnesen
2020-08-21 14:42 ` John Cowan
2020-08-21 15:17 ` Steve Nickolas
2020-08-21 15:23 ` Steffen Nurpmeso
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=5c629889-d4b0-761e-9eb2-76b73ffa097b@case.edu \
--to=chet.ramey@case.edu \
--cc=cowan@ccil.org \
--cc=tuhs@tuhs.org \
--cc=usotsuki@buric.co \
/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).