undocumented variable MAKE_COMMAND

2024-02-09 Thread Frank Heckenbach
I got some strange make errors about resetting jobserver mode etc. Long story short, after some debugging I found the reason: I use an optional wrapper for make which I invoke via an environment variable which I (plausbly) named MAKE_COMMAND. To my surprise, I found that recursive makes using

[bug #65273] Potential bug in the info function?

2024-02-09 Thread Ian Prest
Follow-up Comment #8, bug#65273 (group make): [comment #3 comment #3:] > The problem is that (a) there is no way to create a variable name containing, or consisting of, whitespace Sure there is: Makefile: ``` SPACE := SPACE := $(SPACE) $(SPACE) $(SPACE) := $(SPACE) $(warning [$( )]) ```

[bug #65273] Potential bug in the info function?

2024-02-09 Thread Collin Funk
Follow-up Comment #7, bug#65273 (group make): [comment #6 comment #6:] > Leaving these checks disabled by default is not a good solution since the very people who need this help most, will not benefit from them. I agree. It took me a while to understand some of the GNU Make extensions a few

[bug #65273] Potential bug in the info function?

2024-02-09 Thread Paul D. Smith
Follow-up Comment #6, bug#65273 (group make): I mean, there IS a reasonable way to get the same effect; I showed one possibility in my response. Yes, it looks slightly different but the result is the same and there are no warnings. Alternatively the Emacs makefiles could disable these new