From: Lars Ingebrigtsen <larsi@gnus.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 53358@debbugs.gnu.org
Subject: bug#53358: 29.0.50; Compilation output messed up again
Date: Fri, 21 Jan 2022 10:24:58 +0100 [thread overview]
Message-ID: <87czklwidx.fsf@gnus.org> (raw)
In-Reply-To: <3c5c8f89-86ae-0fa9-9151-773cced53bd9@cs.ucla.edu> (Paul Eggert's message of "Thu, 20 Jan 2022 10:21:17 -0800")
Paul Eggert <eggert@cs.ucla.edu> writes:
> Surely it's just an accident that you've seen it only for ELC, as the
> problem can occur if 'make' executes any two $(info ...)s at about the
> same time.
In principle, but that's the only place I'm seeing this.
> How badly does it occur for you? For me, it's only the first line
> (when many 'makes' start in parallel, which is a glitch I can easily
> ignore.
I see it on every build I do (8 core machine, 16 threads, so I use
-j16). And since the build is so nice and warning-free these days,
those messed-up lines stick out.
> If it's a real annoyance please try the attached patch, which should
> fix the problem for the AM_V_ stuff at the cost of appending annoying
> empty lines with current and older GNU make. (Which annoyance do you
> prefer? :-) You'll need to run './config.status' after applying the
> patch.
Unfortunately there's been other changes in these files, so the patch no
longer applies. But I don't think it makes sense to work around this
problem by making the output look worse for most people, so I'd rather
just avoid using $(info) in the problematic parts -- then it'll look OK
for everybody (and without obfuscation).
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-01-21 9:24 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
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 [this message]
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=87czklwidx.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=53358@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/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).