From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: src/Makefile unhelpful
Date: Wed, 07 Sep 2022 23:00:44 -0400 [thread overview]
Message-ID: <E1oW7mW-00063u-8i@fencepost.gnu.org> (raw)
In-Reply-To: <83bkrrj48w.fsf@gnu.org> (message from Eli Zaretskii on Wed, 07 Sep 2022 05:41:03 +0300)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> > Anyway, I think it would be useful for each make run to output, for
> > debugging, each actual command. It could show each of the usual
> > commands once, or (if it isn't hard) only the usual commands that were
> > actually executed. To show, for instance, what this expands into:
> >
> >
> > at least if the .c.o rule is ever used.
> I think this is rarely needed, so having it silent by default is
> better.
We may be miscommunicating. My idea is that each make run that runs
the command
$(AM_V_CC)$(CC) -c $(CPPFLAGS) $(ALL_CFLAGS) $(PROFILING_CFLAGS)
at least once, should output _just once_ what that expands into.
I agree we do not want to output the expansion more than once.
> The way to see the arguments is to say
> make V=1
The problem with that solution is that by October I certainly won't
remember it.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2022-09-08 3:00 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 2:19 src/Makefile unhelpful Richard Stallman
2022-09-07 2:38 ` Po Lu
2022-09-07 2:41 ` Eli Zaretskii
2022-09-08 3:00 ` Richard Stallman [this message]
2022-09-08 4:51 ` Sam James
2022-09-11 3:38 ` Richard Stallman
2022-09-11 5:34 ` Eli Zaretskii
2022-09-11 9:57 ` Lars Ingebrigtsen
2022-09-11 11:59 ` Po Lu
2022-09-11 12:07 ` Eli Zaretskii
2022-09-11 12:16 ` Lars Ingebrigtsen
2022-09-13 4:07 ` Richard Stallman
2022-09-13 16:11 ` Eli Zaretskii
2022-09-14 20:02 ` Alfred M. Szmidt
2022-09-14 20:05 ` Lars Ingebrigtsen
2022-09-14 20:47 ` Gregory Heytings
2022-09-15 7:14 ` Lars Ingebrigtsen
2022-09-15 7:28 ` Gregory Heytings
2022-09-15 7:32 ` Eli Zaretskii
2022-09-15 7:41 ` Gregory Heytings
2022-09-15 9:07 ` Eli Zaretskii
2022-09-15 14:33 ` Óscar Fuentes
2022-09-15 16:04 ` Gregory Heytings
2022-09-17 10:46 ` Gregory Heytings
2022-09-17 11:20 ` Alan Mackenzie
2022-09-17 16:41 ` Michael Welsh Duggan
2022-09-17 22:59 ` Gregory Heytings
2022-09-17 22:58 ` Gregory Heytings
2022-09-18 10:37 ` Lars Ingebrigtsen
2022-09-18 11:38 ` Gerd Möllmann
2022-09-18 11:53 ` Andreas Schwab
2022-09-18 12:05 ` Gerd Möllmann
2022-09-18 13:48 ` Robert Pluim
2022-09-18 16:40 ` Gregory Heytings
2022-09-18 16:59 ` Andreas Schwab
2022-09-18 21:50 ` Gregory Heytings
2022-09-19 17:20 ` chad
2022-09-19 17:25 ` Eli Zaretskii
2022-09-19 20:42 ` Stefan Monnier
2022-09-18 21:39 ` Gregory Heytings
2022-09-15 13:13 ` Ken Brown
2022-09-15 14:01 ` Gregory Heytings
2022-09-11 15:16 ` Werner LEMBERG
2022-09-12 4:35 ` Richard Stallman
2022-09-08 6:14 ` Eli Zaretskii
2022-09-08 7:29 ` Andreas Schwab
2022-09-08 13:18 ` Stefan Monnier
2022-09-11 3:38 ` Richard Stallman
2022-09-11 5:42 ` Eli Zaretskii
2022-09-14 4:12 ` Richard Stallman
2022-09-14 11:33 ` Eli Zaretskii
2022-09-07 3:11 ` Sam James
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1oW7mW-00063u-8i@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).