On 1/20/22 15:02, Dmitry Goncharov wrote:
Will $(warning) suit your needs?
Although it would fix the interleaved output, it would prepend each log
line with something like "Makefile:231:" which would clutter the log
format Emacs builders are currently used to. The log format is the same
that
On Thu, Jan 20, 2022 at 5:41 PM Paul Eggert wrote:
> I suggested working around the problem in the GNU Emacs Makefiles by
> installing the attached patch. It's a bit of a hack but I couldn't think
> of anything better, other than outputting the information with the shell
> rather than with $(info)
On 1/19/22 23:11, Paul Smith wrote:
I rewrote this function and applied this change:
Oh, that's much nicer than what I sent! Thanks.
I suggested working around the problem in the GNU Emacs Makefiles by
installing the attached patch. It's a bit of a hack but I couldn't think
of anything bette
On Wed, 2022-01-19 at 15:49 -0800, Paul Eggert wrote:
> On 1/19/22 15:28, Paul Eggert wrote:
> > Proposed patch attached.
>
> I see that patch's commit message has the wrong URL for the bug
> report. Here's a fixed patch, attached. Only the commit message is
> changed.
I examined this method and
On 1/19/22 15:28, Paul Eggert wrote:
Proposed patch attached.
I see that patch's commit message has the wrong URL for the bug report.
Here's a fixed patch, attached. Only the commit message is changed.From 1b9f1bb7f95699e9c0d59b177e83c1b3bc3852a0 Mon Sep 17 00:00:00 2001
From: Paul Eggert
Da
I recently modified the Emacs build procedure to use '$(info xxx)'
instead of 'echo xxx' to avoid some fork+execs and simplify
strace-oriented debugging. Unfortunately, Lars Ingebrigtsen reports that
this results in confused output with 'make -j' because $(info xxx)
outputs xxx and the followin
