From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 53358@debbugs.gnu.org
Subject: bug#53358: 29.0.50; Compilation output messed up again
Date: Wed, 19 Jan 2022 11:07:43 +0200 [thread overview]
Message-ID: <83czkot7og.fsf@gnu.org> (raw)
In-Reply-To: <87lezcdtm3.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed, 19 Jan 2022 09:20:36 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Wed, 19 Jan 2022 09:20:36 +0100
>
>
> A while back, Paul fixed the compilation output so that we wouldn't get
> messed-up "make -j16" output, but recently it's started again:
>
> ELC ../lisp/button.elc ELC ../lisp/composite.elc
> ELC ../lisp/buff-menu.elc ELC ../lisp/cus-face.elc
>
> ELC ../lisp/cus-start.elc
> ELC ../lisp/custom.elc
> ELC ../lisp/disp-table.elc ELC ../lisp/dnd.elc
>
> ELC ../lisp/dos-fns.elc
>
> I think I've seen this the past couple of weeks, possibly?
>
> I don't quite recall what Paul's fixes entailed... anybody remember?
> And does anybody know what has changed in this area lately?
Maybe the changeset below?
commit eaa44ca40e8da9ba86e6e03b76b41fd6843661d6
Author: Paul Eggert <eggert@cs.ucla.edu>
AuthorDate: Mon Dec 20 12:14:07 2021 -0800
Commit: Paul Eggert <eggert@cs.ucla.edu>
CommitDate: Mon Dec 20 12:24:04 2021 -0800
Prefer $(info) to @echo
Have GNU Make output some diagnostics directly, instead of forking
and execing a shell to do it.
* GNUmakefile (help):
* doc/lispref/two-volume.make (vol2.pdf, elisp2med-init)
(elisp2-init):
* doc/misc/Makefile.in (echo-info, echo-sources):
* lib-src/Makefile.in (archlibdir, install, check):
* src/verbose.mk.in (AM_V_AR, AM_V_CC, AM_V_CXX, AM_V_CCLD)
(AM_V_CXXLD, AM_V_ELC, AM_V_ELN, AM_V_GEN, AM_V_GLOBALS)
(AM_V_RC):
* test/Makefile.in (subdirs, subdir-targets):
Prefer $(info) to @echo.
* GNUmakefile (MAKECMDGOALS, configure, Makefile):
Prefer $(warning) to @echo >&2.
* src/verbose.mk.in (AM_V_ELN): Output target, like the others.
next prev parent reply other threads:[~2022-01-19 9:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 8:20 bug#53358: 29.0.50; Compilation output messed up again Lars Ingebrigtsen
2022-01-19 8:36 ` Lars Ingebrigtsen
2022-01-19 9:07 ` Eli Zaretskii [this message]
2022-01-19 9:16 ` Lars Ingebrigtsen
2022-01-19 23:32 ` Paul Eggert
2022-01-19 23:53 ` Paul Eggert
2022-01-20 8:10 ` Lars Ingebrigtsen
2022-01-20 18:21 ` Paul Eggert
2022-01-21 9:24 ` Lars Ingebrigtsen
2022-01-21 22:52 ` Paul Eggert
2022-01-22 10:16 ` Lars Ingebrigtsen
2022-01-24 7:25 ` Paul Eggert
2022-01-24 9:47 ` Lars Ingebrigtsen
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=83czkot7og.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=53358@debbugs.gnu.org \
--cc=larsi@gnus.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).