[bug #58639] Shortest stem not matched

Follow-up Comment #3, bug #58639 (project make): I changed the text like this; hopefully it's more understandable now: target pattern that matches the file name, @emph{and} all prerequisites in that rule either exist or can be built. The rules you write take precedence over those that are

[bug #58656] Cannot handle over 2GB file on Windows

Follow-up Comment #3, bug #58656 (project make): @eliz did you have any comments on the second form of this patch or should I apply it? Cheers! ___ Reply to this item at:

[bug #51286] Support for additional local make variables

Update of bug #51286 (project make): Status:None => Fixed Assigned to:None => psmith Open/Closed:Open => Closed Fixed Release:

Re: [PATCH 1/2] * src/function.c: Introduce the 'let' built-in function

On Fri, 2020-10-23 at 09:14 -0400, Paul Smith wrote: > On Fri, 2020-10-09 at 16:36 +0200, Jouke Witteveen wrote: > > > This was sent before at the end of last year. Meanwhile, the > > copyright of my contributions is assigned to the FSF, so I picked > > this up again and added some documentation

Re: [PATCH 2/2 V2] * doc/make.texi: Document the let function

On Sat, 2020-10-10 at 17:50 -0500, Pete Dietl wrote: > Also, I ran ‘’make html”, but it doesn’t look like it does on he > website. Does anyone know how I can build the docs to look like the > website locally? It's not so easy to do unfortunately. It requires a bunch of prerequisites, that are

Re: GNU Make 4.3: Makefile rule spooky action at a distance

On Sun, 2020-10-04 at 09:11 +0200, Danny Milosavljevic wrote: > I just got a build failure in lz4. I've isolated it and made a > minimal test case, see below. > > This is on GNU Guix on a x86_64 machine. > > The reason is that apparently one Makefile rule can unwittingly > change how another

Re: notes about make docs p 3.5

On Thu, 2020-12-03 at 15:04 +0300, Dmitry wrote: > > > It'll be very good to have some examples with explanations in the > > > docs. > > Maybe so. Concrete suggestions are easy to discuss, like: > > I think this example would saved me a lot of time. > > make -f mkfile > > content of mkfile: >

[bug #58960] Fix a typo in the manual

Update of bug #58960 (project make): Status:None => Fixed Assigned to:None => psmith Open/Closed:Open => Closed Fixed Release:

[bug #58961] Document dynamic phony targets.

Update of bug #58961 (project make): Status:None => Fixed Assigned to:None => psmith Open/Closed:Open => Closed Fixed Release:

[bug #54816] $(wildcard ...) function does not report dangling symlinks

Update of bug #54816 (project make): Status:None => Not A Bug Open/Closed:Open => Closed ___ Follow-up Comment #3: This issue appears to

[bug #47752] --no-print-directory has no effect if command parsing complains about -j options

Follow-up Comment #2, bug #47752 (project make): Turns out that this fix is present in 4.3, not 4.2. Updated this bug to have correct metadata. ___ Reply to this item at:

[bug #47752] --no-print-directory has no effect if command parsing complains about -j options

Update of bug #47752 (project make): Status: Duplicate => Fixed Assigned to:None => psmith Fixed Release:None => 4.3

[bug #59467] --no-print-directory has no effect if command parsing complains about -j options

Update of bug #59467 (project make): Status:None => Duplicate Open/Closed:Open => Closed ___ Follow-up Comment #1: This works properly

[bug #59169] Add a --debug=why category for the -d/--debug option

Follow-up Comment #5, bug #59169 (project make): I'd consider this change too small to require attribution so not to worry! ___ Reply to this item at:

[bug #59584] ifeq with a space after the first open parenthesis

Update of bug #59584 (project make): Item Group: Bug => Enhancement ___ Follow-up Comment #1: The reason this happens is that for conditionals, preceding whitespace is preserved in the

[bug #59585] Make with output-sync prints 'fcntl(): Bad file descriptor' on MacOS when output is piped

Update of bug #59585 (project make): Status:None => Duplicate Open/Closed:Open => Closed ___ Follow-up Comment #1: This is a duplicate

[bug #59601] buffer over-read on malformed environment variable

Update of bug #59601 (project make): Status:None => Fixed Assigned to:None => psmith Open/Closed:Open => Closed Fixed Release:

[bug #59169] Add a --debug=why category for the -d/--debug option

Update of bug #59169 (project make): Status:None => Fixed Assigned to:None => psmith Open/Closed:Open => Closed Operating System:

[bug #58836] build.sh is not populated in objects directory when running configure

Update of bug #58836 (project make): Status:None => Fixed Assigned to:None => psmith Open/Closed:Open => Closed Fixed Release:

[bug #57676] openjdk11 fails to build with make 4.3

Update of bug #57676 (project make): Status:None => Fixed Assigned to:None => psmith Open/Closed:Open => Closed Fixed Release: