Compilation error on master branch (Commit c5d4b7b)

Dear GNU Make maintainers, I just cloned Make (with the 'master' branch on commit c5d4b7b2f260c). I also pulled the most recent changes in Gnulib's 'master' branch (putting me on Gnulib commit dd0af10fa597a) and bootstrapped Make. I then ran the standard './configure' and 'make' commands to b

Re: Compilation error on master branch (Commit c5d4b7b)

On Sun, 2021-10-03 at 23:23 +0200, Mohammad Akhlaghi wrote: > I then ran the standard './configure' and 'make' commands to build > it, but the build failed with the attached error messages when > building 'src/guile.c'. These errors appear to be coming from compiling src/read.c, not src/guile.c.

Re: Compilation error on master branch (Commit c5d4b7b)

On 10/3/21 23:38, Paul Smith wrote: On Sun, 2021-10-03 at 23:23 +0200, Mohammad Akhlaghi wrote: I then ran the standard './configure' and 'make' commands to build it, but the build failed with the attached error messages when building 'src/guile.c'. These errors appear to be coming from compil

[bug #61226] A regression prevents generation of missing included dependency files.

Follow-up Comment #5, bug #61226 (project make): > When you say the special behavior do you mean the section "Rules without Recipes or Prerequisites"? exactly > I think that text is a little misleading. There's actually nothing magical about having no recipe or an empty recipe here, as best as

[bug #61226] A regression prevents generation of missing included dependency files.

Additional Item Attachment, bug #61226 (project make): File name: sv_61226_no_build_on_missing_includes.diff Size:1 KB ___ Reply to this ite

[bug #61226] A regression prevents generation of missing included dependency files.

Follow-up Comment #6, bug #61226 (project make): It is disturbing that the warning is printed each time a .d file is missing. In other words, make prints a warning in an everything goes as planned situation, like a clean build. Switching to -include robs the user of a useful message, should there