From: lyndon@orthanc.ca (Lyndon Nerenberg)
Subject: [TUHS] Another "make-raking" discussion topic
Date: Sat, 23 Sep 2017 11:09:03 -0700 [thread overview]
Message-ID: <2A1C2147-5B89-4579-9D9B-29E62AC7DA66@orthanc.ca> (raw)
In-Reply-To: <1506182039.27660.for-standards-violators@oclsc.org>
> On Sep 23, 2017, at 8:53 AM, Norman Wilson <norman at oclsc.org> wrote:
>
> As with any other language, of course, it's best to use it
> in as simple a way as possible. So I don't care much whether
> it's gmake or pmake or qmake as long as it implements more
> or less the 7/e core subset without breaking anything.
For my Makefiles, I almost always add
.POSIX:
as the first line, to avoid inadvertently using [bgp]make extensions.
prev parent reply other threads:[~2017-09-23 18:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-23 15:53 Norman Wilson
2017-09-23 18:09 ` Lyndon Nerenberg [this message]
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=2A1C2147-5B89-4579-9D9B-29E62AC7DA66@orthanc.ca \
--to=lyndon@orthanc.ca \
/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).