public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: "bug-make@gnu.org" <bug-make@gnu.org>, Paul Smith <psmith@gnu.org>
Cc: Sergei Trofimovich <slyich@gmail.com>,
	linux-man <linux-man@vger.kernel.org>
Subject: Usefulness of make -t
Date: Sun, 2 Apr 2023 14:20:11 +0200	[thread overview]
Message-ID: <00fce115-146e-0501-4449-5366be048eef@gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 975 bytes --]

Hi Paul,

Yesterday I found another use of make's -t flag: It helps make sure
that the logic in the Makefile is correct.  You could run the target
without -t, but then you risk seeing warnings and errors from the
commands run by the target before make's own ones, which would hide
Makefile problems.

If you run `make -kstj [target(s)]` after modifying a Makefile, it
will show only and all^Wmost problems in the Makefile itself.  It
could be especially useful with 4.4's --shuffle, although I don't
have it yet in Debian Sid :(.  I should build from source and try it.

I'll start using that as a rule to check changes to Makefiles, and
hopefully will avoid introducing bugs that I need to fix in the next
commit :)

<https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/?id=5bf82f50cf02ded2403666d6c1ee2878b8bd602e>

Cheers,
Alex


-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2023-04-02 12:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-02 12:20 Alejandro Colomar [this message]
2023-04-02 13:16 ` Usefulness of make -t Alejandro Colomar

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=00fce115-146e-0501-4449-5366be048eef@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=bug-make@gnu.org \
    --cc=linux-man@vger.kernel.org \
    --cc=psmith@gnu.org \
    --cc=slyich@gmail.com \
    /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