[bug #48643] Irrelevant targets can confuse make on which pattern rule to select.

Follow-up Comment #32, bug #48643 (project make): There are too many patches attached to this bug: I lost track of which had been applied and which hadn't and I guess I missed that one; sorry about that! The change in 6682fb was discussed in this email to bug-make:

[bug #61864] incorrect debug output

Follow-up Comment #1, bug #61864 (project make): I applied this, thanks. ___ Reply to this item at: ___ Message sent via Savannah

Re: $(info xxx) output interleaved with other $(info) output

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

[bug #48643] Irrelevant targets can confuse make on which pattern rule to select.

Follow-up Comment #31, bug #48643 (project make): Paul, in update 27 i added 2 patches. sv48643_exp_preqreq_is_not_interm.diff has a fix for example 6. sv48643_exp_preqreq_is_not_interm_tests.diff has related tests. Not sure, if you decided not to apply these 2 patches or they fell through the

[bug #61864] incorrect debug output

Additional Item Attachment, bug #61864 (project make): File name: sv61864_fix.diff Size:0 KB ___ Reply to this item at:

[bug #61864] incorrect debug output

URL: Summary: incorrect debug output Project: make Submitted by: dgoncharov Submitted on: Thu 20 Jan 2022 02:30:58 AM UTC Severity: 3 - Normal Item Group: Bug

[bug #48643] Irrelevant targets can confuse make on which pattern rule to select.

Follow-up Comment #30, bug #48643 (project make): > Let us list the options > 1. keep compat search enabled by default and silent. > 2. introduce a warning message when make begins compat search. > 3. introduce a flag to disable compat search. > 4. have compat disabled by default and introduce a

Re: Invalid use of const pointer?

On Tue, 2022-01-18 at 10:56 -0500, Joe Filion wrote: > I could recommend changing line 557 to something like: > > const char * cp = strchr (nptr, ‘%’); Good idea, thanks. I cleaned up this section of code.

Re: $(info xxx) output interleaved with other $(info) output

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

$(info xxx) output interleaved with other $(info) output

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

Re: Linux /proc/loadavg

On Sat, 2022-01-15 at 10:29 +, Sven C. Dack wrote: > I have recently been looking into this again, because of a new > feature I am currently testing, and so far can only repeat what I > have already said in the past. The /proc/loadavg file under Linux > with a vanilla kernel is behaving as