[bug #54533] Touching an archive member leaves a NUL byte after date field

URL: Summary: Touching an archive member leaves a NUL byte after date field Project: make Submitted by: None Submitted on: Sat 18 Aug 2018 03:01:18 PM UTC Severity: 3 - Normal

[bug #52697] More varieties to -j switch

Follow-up Comment #3, bug #52697 (project make): I'm pretty sure something like this was already proposed, discussed and/or even implemented somewhere, but anyway: here is a quick and dirty hack I'm using to successfully compile gcc (together with some other required measures) on my raspberry pi

[bug #54549] Segfault caused by makefile in make version 4.2.1

URL: Summary: Segfault caused by makefile in make version 4.2.1 Project: make Submitted by: None Submitted on: Tue 21 Aug 2018 10:19:50 PM UTC Severity: 3 - Normal Item G

[bug #54875] The + prefix in canned recipe affects multiple lines

URL: Summary: The + prefix in canned recipe affects multiple lines Project: make Submitted by: None Submitted on: Mon 22 Oct 2018 01:38:12 PM UTC Severity: 3 - Normal It

[bug #55242] Included Makefile not found, no rule to build it but make does not fail

URL: Summary: Included Makefile not found, no rule to build it but make does not fail Project: make Submitted by: None Submitted on: Wed 19 Dec 2018 12:37:06 PM UTC Severity: 3 - Norm

[bug #55532] Missing prerequisites are not included in $^ if .SECONDARY is present

URL: Summary: Missing prerequisites are not included in $^ if .SECONDARY is present Project: make Submitted by: None Submitted on: Mon 21 Jan 2019 01:03:46 AM UTC Severity: 3 - Normal

[bug #55533] .SECONDARY with % pattern

URL: Summary: .SECONDARY with % pattern Project: make Submitted by: None Submitted on: Mon 21 Jan 2019 01:38:58 AM UTC Severity: 3 - Normal Item Group: Enhancement

[bug #55533] .SECONDARY with % pattern

Follow-up Comment #1, bug #55533 (project make): The correct command of 'Result 2' is as follows: Result 2 $ rm -f a.* $ touch a.zzz $ make a.xxx cp a.zzz a.yyy cp a.yyy a.xxx rm a.yyy ___ Reply to this item at:

[bug #55532] Missing prerequisites are not included in $^ if .SECONDARY is present

Follow-up Comment #1, bug #55532 (project make): Maybe, is it better to check other special targets as well? '.PRECIOUS: bar' does not interfere the $^, but I see similar weirdness for '.INTERMEDIATE: bar'. ___ Reply to this item at: <

[bug #55560] .SECONDEXPANSION and eval in target-specific prerequisite lists

URL: Summary: .SECONDEXPANSION and eval in target-specific prerequisite lists Project: make Submitted by: None Submitted on: Thu 24 Jan 2019 04:33:32 PM UTC Severity: 3 - Normal

[bug #55757] FR: strict variable substitution

URL: Summary: FR: strict variable substitution Project: make Submitted by: None Submitted on: Thu 21 Feb 2019 08:38:59 PM UTC Severity: 3 - Normal Item Group: Enhancemen

[bug #55757] FR: strict variable substitution

Follow-up Comment #1, bug #55757 (project make): Try setting: .SHELLFLAGS := -u -c ___ Reply to this item at: ___ Message sent via Savannah https://

[bug #55757] FR: strict variable substitution

Follow-up Comment #3, bug #55757 (project make): Is --warn-undefined variables not sufficient? If you want to fail recipes, would it be feasible to set the shell to bash, and then set 'nounset' in the prolog of each recipe? ___ Reply to t

[bug #55757] FR: strict variable substitution

Follow-up Comment #4, bug #55757 (project make): That's really close to what I want! A fail-undefined-variables would be even closer, if the team feels it's a good addition. ___ Reply to this item at:

[bug #56420] Unclear wording or missing word

URL: Summary: Unclear wording or missing word Project: make Submitted by: None Submitted on: Thu 30 May 2019 08:15:34 PM UTC Severity: 3 - Normal Item Group: Documentati

[bug #56422] How to find the number of rules in GMAKE

URL: Summary: How to find the number of rules in GMAKE Project: make Submitted by: None Submitted on: Fri 31 May 2019 03:03:24 AM UTC Severity: 3 - Normal Item Group: En

[bug #56449] job.c (construct_command_argv_internal): Must use shell if '%' character is present in recipe line

URL: Summary: job.c (construct_command_argv_internal): Must use shell if '%' character is present in recipe line Project: make Submitted by: None Submitted on: Thu 06 Jun 2019 11:13:33 AM UTC

[bug #56484] [RFE] compile modified files first

URL: Summary: [RFE] compile modified files first Project: make Submitted by: None Submitted on: Wed 12 Jun 2019 09:07:39 PM UTC Severity: 3 - Normal Item Group: Enhancem

[bug #39310] Regression in glob-handling from 3.81, can't use a stem and a glob in the same dependency

Follow-up Comment #2, bug #39310 (project make): The patch for this bug broke making files whose name contains a space, using a pattern rule. ___ Reply to this item at:

[bug #56655] Pattern rule fails when filename contains a space

URL: Summary: Pattern rule fails when filename contains a space Project: make Submitted by: None Submitted on: Mon 22 Jul 2019 07:27:57 AM UTC Severity: 3 - Normal Item

[bug #56701] Do not allow -j without a number

URL: Summary: Do not allow -j without a number Project: make Submitted by: None Submitted on: Wed 31 Jul 2019 02:55:34 PM UTC Severity: 3 - Normal Item Group: Bug

[bug #56655] Pattern rule fails when filename contains a space

Additional Item Attachment, bug #56655 (project make): File name: Makefile Size:0 KB ___ Reply to this item at: __

[bug #56732] VPATH doesn't work with pattern rules

URL: Summary: VPATH doesn't work with pattern rules Project: make Submitted by: None Submitted on: Thu 08 Aug 2019 11:26:35 AM UTC Severity: 3 - Normal Item Group: Bug

[bug #56732] VPATH doesn't work with pattern rules

Follow-up Comment #1, bug #56732 (project make): Your example doesn't seem to rely on VPATH in any way. Remember: VPATH is used as a place to look for files. Also you are using "-lAbc" as prerequisite for output/%. It seems you are intending to use linker flags as input to the recipe. The way you

[bug #56732] VPATH doesn't work with pattern rules

Follow-up Comment #2, bug #56732 (project make): Thanks for looking at this. Make supports linker flags as dependencies of a recipe and automatically searches for the .a/.so file using VPATH. See the relevant section of the manual, 4.5.6 "Directory Search for Link Libraries". I should have emphas

[bug #56732] VPATH doesn't work with pattern rules

Follow-up Comment #3, bug #56732 (project make): OK, this is a special case I didn't remembered. The wording in the manual doesn't touch implicit rules, so one can assume it should work for them too. I don't know how much application of rules differs between normal and implicit ones, so I can't h

[bug #56019] Decreased parallelization vs. Make 3.82

Follow-up Comment #1, bug #56019 (project make): Hit the same bug in version 4.2.1 while building "allnoconfig" linux kernel. For me bug triggers rarely, 1 in 30 cases. It looks like the bug is fixed in the current git tree. ___ Reply to t

[bug #56019] Decreased parallelization vs. Make 3.82

Follow-up Comment #2, bug #56019 (project make): Commits for bug #51159 and bug #51400 together fix the problem for me: commit 78b5fec6898c26956d00548427cda1101cb80f8a Author: Paul Smith Date: Sun Jul 9 18:44:17 2017 -0400 [SV 51400] Only unblock fatal signals after child invocation com

[bug #56834] PATH not honored when --disable-posix-spawn is not used

URL: Summary: PATH not honored when --disable-posix-spawn is not used Project: make Submitted by: None Submitted on: Fri 30 Aug 2019 12:20:12 PM UTC Severity: 3 - Normal

[bug #56872] Overriding a recipe without warning message

URL: Summary: Overriding a recipe without warning message Project: make Submitted by: None Submitted on: Sun 08 Sep 2019 06:27:18 PM UTC Severity: 3 - Normal Item Group:

[bug #56875] subst failure for "$" character

URL: Summary: subst failure for "$" character Project: make Submitted by: None Submitted on: Mon 09 Sep 2019 02:13:17 PM UTC Severity: 3 - Normal Item Group: Bug

[bug #56914] Most output missing when building with --output-sync

URL: Summary: Most output missing when building with --output-sync Project: make Submitted by: None Submitted on: Tue 17 Sep 2019 02:34:11 PM UTC Severity: 3 - Normal It

[bug #56918] endless loop under Darwin if recipe is non_existent_program

URL: Summary: endless loop under Darwin if recipe is non_existent_program Project: make Submitted by: None Submitted on: Wed 18 Sep 2019 08:25:19 PM UTC Severity: 3 - Normal

[bug #57014] make-4.2.91 segfaults under Solaris 10 when many files are involved

URL: Summary: make-4.2.91 segfaults under Solaris 10 when many files are involved Project: make Submitted by: None Submitted on: Mon 07 Oct 2019 01:01:57 PM UTC Severity: 3 - Normal

[bug #57014] make-4.2.91 segfaults under Solaris 10 when many files are involved

Follow-up Comment #2, bug #57014 (project make): Inserting many fprintf() incantations into the source code shows that glob (name, GLOB_ALTDIRFUNC, NULL, &gl) (line 3391 of src/read.c) seems the responsible. ___ Reply to this item at:

[bug #57014] make-4.2.91 segfaults under Solaris 10 when many files are involved

Follow-up Comment #3, bug #57014 (project make): Please have a look into src/hash.c, in sum_up_to_nul(). The memcpy() (line 416) segfaults because the bytes after \0 are not readable, in the case where the filename (or whatever is hashed here) ends immediately (or almost immediately) before the bo

[bug #57014] make-4.2.91 segfaults under Solaris 10 when many files are involved

Follow-up Comment #5, bug #57014 (project make): Thank you. Indeed it is solved in 4.2.92. ___ Reply to this item at: ___ Message sent via Savannah h

[bug #57022] Error 127 executing a script with no #!

Follow-up Comment #1, bug #57022 (project make): I add that if the Makefile contains the line SHELL = /bin/bash the behaviour of make-4.2.92 is iaw make-4.2.1 (that is the bug does not show up). This is perhaps not enough explicit in the original bug report. In other words, to be able to run you

[bug #57022] Error 127 executing a script with no #!

Follow-up Comment #2, bug #57022 (project make): I forgot to say that SHELL = /bin/sh does _not_ work, you have to use SHELL = /bin/bash Denis Excoffier. ___ Reply to this item at: ___

[bug #57365] Makefile autocomplete is puzzled with lines starting with spaces

URL: Summary: Makefile autocomplete is puzzled with lines starting with spaces Project: make Submitted by: None Submitted on: Thu 05 Dec 2019 02:26:33 PM UTC Severity: 3 - Normal

[bug #57625] Shell builtins not working unless explicitly set SHELL to "sh"

URL: Summary: Shell builtins not working unless explicitly set SHELL to "sh" Project: make Submitted by: None Submitted on: Sat 18 Jan 2020 12:48:39 PM UTC Severity: 3 - Normal

[bug #57672] Hard to read type-o

URL: Summary: Hard to read type-o Project: make Submitted by: None Submitted on: Mon 27 Jan 2020 06:49:21 AM UTC Severity: 3 - Normal Item Group: Documentation

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

Follow-up Comment #3, bug #57676 (project make): > (I tried to send this to -email is unavailable- but it appears to have disappeared somewhere) (I got it and your other one, but raising a bug was probably a better choice anyway here.) > fails on first run with make 4.3 martind@paris:~/tmp/make-

[bug #57866] make fails to recognize dependency and substitute variables

URL: Summary: make fails to recognize dependency and substitute variables Project: make Submitted by: None Submitted on: Thu 20 Feb 2020 09:00:41 AM UTC Severity: 3 - Normal

[bug #57896] Incorrect directory is printed in "Entering directory" message when -j1 disables jobserver mode for a sub make

URL: Summary: Incorrect directory is printed in "Entering directory" message when -j1 disables jobserver mode for a sub make Project: make Submitted by: None Submitted on: Tue 25 Feb 2020 05:09:22 PM

[bug #57898] Automatic variable for all targets on grouped target

URL: Summary: Automatic variable for all targets on grouped target Project: make Submitted by: None Submitted on: Tue 25 Feb 2020 08:09:08 PM UTC Severity: 3 - Normal It

[bug #57930] plain char arguments to functions

URL: Summary: plain char arguments to functions Project: make Submitted by: None Submitted on: Sun 01 Mar 2020 01:10:01 PM UTC Severity: 3 - Normal Item Group: None

[bug #57967] make messes up the terminal

URL: Summary: make messes up the terminal Project: make Submitted by: None Submitted on: Sat 07 Mar 2020 12:07:51 PM UTC Severity: 3 - Normal Item Group: Bug

[bug #58013] .SILENT appears to be ignored in GNU Make 4.3

URL: Summary: .SILENT appears to be ignored in GNU Make 4.3 Project: make Submitted by: None Submitted on: Fri 20 Mar 2020 08:06:48 AM UTC Severity: 3 - Normal Item Grou

[bug #58056] Forced prerequisite order is not honored with pattern rules

URL: Summary: Forced prerequisite order is not honored with pattern rules Project: make Submitted by: None Submitted on: Fri 27 Mar 2020 11:14:42 AM UTC Severity: 3 - Normal

[bug #58075] compiler warning: add explicit braces to avoid dangling else

URL: Summary: compiler warning: add explicit braces to avoid dangling else Project: make Submitted by: None Submitted on: Sun 29 Mar 2020 01:35:17 PM UTC Severity: 3 - Normal

[bug #58056] Forced prerequisite order is not honored with pattern rules

Follow-up Comment #2, bug #58056 (project make): [comment #1 comment #1:] > This behavior is intended. > [...] > 2. Another reason is to allow parallel execution. If all prerequisites had to be built in the specified order how would you built them in parallel? Did you notice the '|'? foo_A and fo

[bug #58056] Forced prerequisite order is not honored with pattern rules

Follow-up Comment #5, bug #58056 (project make): [comment #3 comment #3:] > make builds order only prerequisites in parallel. How can the ordering on the rules be respected then? ___ Reply to this item at:

[bug #58056] Forced prerequisite order is not honored with pattern rules

Follow-up Comment #6, bug #58056 (project make): [comment #4 comment #4:] > So I claim that parallel make and order-only prerequisites are distractions here. We should start with the documentation: what does it guarantee about the build order of the prereqs in the example makefile variants, in a s

[bug #58056] Forced prerequisite order is not honored with pattern rules

Follow-up Comment #12, bug #58056 (project make): If this behavior is allowed, I think the documentation should clarify what the order-only prerequisites actually means. I still haven't figured out their purpose or how they operate based on the documentation or what has been said here. To me, the

[bug #58347] Build failure on 32-bit ARM

URL: Summary: Build failure on 32-bit ARM Project: make Submitted by: None Submitted on: Mon 11 May 2020 01:56:14 AM UTC Severity: 3 - Normal Item Group: Bug

[bug #58365] make 4.3 segfault on s390x alpine linux

URL: Summary: make 4.3 segfault on s390x alpine linux Project: make Submitted by: None Submitted on: Wed 13 May 2020 02:17:33 PM UTC Severity: 3 - Normal Item Group: Bug

[bug #57962] make attempts to execute a directory found on PATH

Follow-up Comment #12, bug #57962 (project make): [comment #7 comment #7:] > I verified this fix was applied to gnulib, so it will be present in the next release of GNU make. Thanks! It seems that gnulib fixed findprog but not findprog_in that GNU make uses so the bug is still present. _

[bug #58435] make 4.3 is not c89 compliant

URL: Summary: make 4.3 is not c89 compliant Project: make Submitted by: None Submitted on: Sat 23 May 2020 10:35:54 PM UTC Severity: 3 - Normal Item Group: Build/Install

[bug #58435] make 4.3 is not c89 compliant

Follow-up Comment #1, bug #58435 (project make): i probably worded the title badly. the fact that gnu make requires c99 features is not a problem, but if it does require c99, then this should be clear and the configure script should be checking for c99 support and adding flags if necessary. howe

[bug #58435] make 4.3 is not c89 compliant

Follow-up Comment #3, bug #58435 (project make): perhaps the maintainers of gnulib ought to be notified of this also... gnu's coding standards state that c89 should be the default targeted c standard, and c99 functionality should be checked for if used. if gnulib is using c99 features, and is mea

[bug #58472] Modernization of the include path

URL: Summary: Modernization of the include path Project: make Submitted by: None Submitted on: Sun 31 May 2020 07:13:43 PM UTC Severity: 3 - Normal Item Group: Enhanceme

[bug #58734] gmake does not check for the existence of a file before complaining it is missing

Follow-up Comment #3, bug #58734 (project make): > directory caching ... which I was convinced was flawed in: https://lists.gnu.org/archive/html/bug-make/2016-10/msg00019.html I bet that's not the problem here, but, until we see the example Dmitry requested... _

[bug #58743] siggetmask should be called with no arguments.

URL: Summary: siggetmask should be called with no arguments. Project: make Submitted by: None Submitted on: Fri 10 Jul 2020 06:28:55 AM UTC Severity: 3 - Normal Item Gro

[bug #58743] siggetmask should be called with no arguments.

Follow-up Comment #2, bug #58743 (project make): I forgot to mention it is for RPi which is arm. It may be related to: [bug #58347] Build failure on 32-bit ARM ___ Reply to this item at: _

[bug #58743] siggetmask should be called with no arguments.

Follow-up Comment #3, bug #58743 (project make): Now works well with tcc and you last commit. In fact, I had to remove -C (comment) gcc option which is not supported by tcc. Maybe you should test if $(CC) supports -C. I also tested on RPi 64bit which is aarch64 not arm.

[bug #58743] siggetmask should be called with no arguments.

Follow-up Comment #6, bug #58743 (project make): That's fine with me. I was using git to test your recent changes on Raspberry (arm) and now confirm it works well. I was not aware it builds gnumake in maintenance mode. Thanks your for your help and support. Christian ___

[bug #58743] siggetmask should be called with no arguments.

Follow-up Comment #7, bug #58743 (project make): FYI I just pushed -C (empty) support to tcc git. tcc has already several gcc compatible options that are accepted but dropped in order to support gcc plug and play replacement. Now, with or without maintainer mode, gnumake compiles ROOTB from git w

[bug #58794] Missing INSTALL file in GNU Make 4.3 archive

URL: Summary: Missing INSTALL file in GNU Make 4.3 archive Project: make Submitted by: None Submitted on: Tue 21 Jul 2020 06:17:59 AM UTC Severity: 3 - Normal Item Group

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

URL: Summary: build.sh is not populated in objects directory when running configure Project: make Submitted by: None Submitted on: Mon 27 Jul 2020 09:40:21 AM UTC Severity: 3 - Normal

[bug #58845] In would be nice to have "$&" expand to all targets in a grouped target

URL: Summary: In would be nice to have "$&" expand to all targets in a grouped target Project: make Submitted by: None Submitted on: Tue 28 Jul 2020 08:55:11 PM UTC Severity: 3 - Norm

[bug #58979] Recursive make using jobserver hangs at completion

URL: Summary: Recursive make using jobserver hangs at completion Project: make Submitted by: None Submitted on: Tue 18 Aug 2020 10:07:20 PM UTC Severity: 3 - Normal Item

[bug #48276] Better errors for accidental spaces

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

[bug #59154] Multiline environment variables handled poorly

Follow-up Comment #3, bug #59154 (project make): Since, IN THIS CASE, the value should really only be processed once, isn't the solution to defer the expansion to the shell by using echo PUB is "$${PUB}" as the recipe? ___ Reply to

[bug #59154] Multiline environment variables handled poorly

Follow-up Comment #5, bug #59154 (project make): (To be precise, the line echo "${BLAH}" works in all the shells I've tested, and in BSD Make, but not GNU Make. If BSD Make can get this right, seems like gnu make should be able to, too.) ___

[bug #59154] Multiline environment variables handled poorly

Follow-up Comment #7, bug #59154 (project make): If the string isn't quoted, the first newline would naturally signal a new command to the shell, wouldn't it? Got an example of a real-world Makefile that would break? ___ Reply to this item

[bug #59154] Multiline environment variables handled poorly

Follow-up Comment #4, bug #59154 (project make): "Newlines in variable expansions are treated as real newlines in the rule." Well, yes, of course. What I didn't expect is for the command to be truncated at the first newline. The shell script BLAH="hi there" export BLAH echo "$BLAH" properly

[bug #59154] Multiline environment variables handled poorly

Follow-up Comment #9, bug #59154 (project make): I don't think this would require Make to parse double quotes. My guess is it would mean passing along expanded variables to the shell without parsing the variable contents for newlines. If I have time, maybe I'll have a look at whether my guess is

[bug #59154] Multiline environment variables handled poorly

Follow-up Comment #14, bug #59154 (project make): [comment #10 comment #10:] > GNU makefiles will allow the following makefile: > > > define SOMECOMMAND > cd foo && echo one > cd foo && echo two > endef > > all: ; $(SOMECOMMAND) > > > to print both "one" and "two" when there is a subdirectory

[bug #59154] Multiline environment variables handled poorly

Follow-up Comment #15, bug #59154 (project make): Also: I have great respect for the difficulty of getting stuff like this right. (I recently stared down the maw of commandline issues in response files in meson... https://github.com/mesonbuild/meson/pull/7245 ) so while I may have sounded glib, I

[bug #59211] Add a commandline option to print the executed command with unexpanded variables

URL: Summary: Add a commandline option to print the executed command with unexpanded variables Project: make Submitted by: None Submitted on: Thu 01 Oct 2020 07:43:20 AM UTC Severity:

[bug #59243] Overcomplicated example of automatic dependency configuration

URL: Summary: Overcomplicated example of automatic dependency configuration Project: make Submitted by: None Submitted on: Fri 09 Oct 2020 03:49:50 PM UTC Severity: 3 - Normal

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

URL: Summary: --no-print-directory has no effect if command parsing complains about -j options Project: make Submitted by: None Submitted on: Mon 16 Nov 2020 07:46:31 PM UTC Severity:

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

URL: Summary: ifeq with a space after the first open parenthesis Project: make Submitted by: None Submitted on: Tue 01 Dec 2020 03:55:44 AM UTC Severity: 3 - Normal Item

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

URL: Summary: Make with output-sync prints 'fcntl(): Bad file descriptor' on MacOS when output is piped Project: make Submitted by: None Submitted on: Tue 01 Dec 2020 11:10:50 AM UTC

[bug #59691] feature requests: something similiar to __LINE__ and __FILE__ in C

URL: Summary: feature requests: something similiar to __LINE__ and __FILE__ in C Project: make Submitted by: None Submitted on: Tue 15 Dec 2020 02:06:22 PM UTC Severity: 3 - Normal

[bug #59762] make --touch produce local spurious empty files with out-of-tree Makefile strategy

URL: Summary: make --touch produce local spurious empty files with out-of-tree Makefile strategy Project: make Submitted by: None Submitted on: Thu 24 Dec 2020 03:43:44 PM UTC Severit

[bug #59881] Segmentation Fault through manipulated Makefile

URL: Summary: Segmentation Fault through manipulated Makefile Project: make Submitted by: None Submitted on: Fri 15 Jan 2021 01:18:53 PM UTC Severity: 3 - Normal Item Gr

[bug #59956] Recipes inside conditionals can break the parser

URL: Summary: Recipes inside conditionals can break the parser Project: make Submitted by: None Submitted on: Wed 27 Jan 2021 08:29:00 PM UTC Severity: 3 - Normal Item

[bug #59956] Recipes inside conditionals can break the parser

Follow-up Comment #5, bug #59956 (project make): > We can "fix" it by adding a simplifying heuristic; perhaps something like: "conditional statements are only recognized if they are not prefixed by the recipe prefix in effect when the if-statement started". That is not perfect but it's probably g

[bug #60165] Multiple pattern rules with single rule

URL: Summary: Multiple pattern rules with single rule Project: make Submitted by: None Submitted on: Wed 03 Mar 2021 09:24:53 PM UTC Severity: 3 - Normal Item Group: Enh

[bug #60281] Directory in directory in $PATH shadows binaries in $PATH

URL: Summary: Directory in directory in $PATH shadows binaries in $PATH Project: make Submitted by: None Submitted on: Tue 23 Mar 2021 09:50:35 PM UTC Severity: 3 - Normal

[bug #60312] echo replaces double quote with backslash

URL: Summary: echo replaces double quote with backslash Project: make Submitted by: None Submitted on: Tue 30 Mar 2021 08:22:32 PM UTC Severity: 3 - Normal Item Group: B

[bug #60312] echo replaces double quote with backslash

Follow-up Comment #2, bug #60312 (project make): Yes, you're right. I thought echo was an internal command. I investigated further and the culprit seems to be the POSIX emulation library, which does strange things trying to emulate shell globbing. Sorry for the inconvenience, please discard this

[bug #60312] echo replaces double quote with backslash

Follow-up Comment #4, bug #60312 (project make): I do have it: $ which sh /usr/bin/sh but make seems to be calling echo.exe directly. Extracts from "strace make -f tm": 0 0 [main] echo (7896) ** 155 155 [main] echo (7896) Program nam

[bug #60312] echo replaces double quote with backslash

Follow-up Comment #5, bug #60312 (project make): And one more thing, this is the respective line output by make -d: CreateProcess(C:\msys64\usr\bin\echo.exe,echo \"xx\",...) I don't know if those backslashes are just added by the log routine or are actually sent by make to echo (in which case,

[bug #60312] echo replaces double quote with backslash

Follow-up Comment #8, bug #60312 (project make): Yeah, well. But if it assumes the invoked program can interpret "backslash double quote" in the command line, why can't it also assume that it can understand "single quote quoting" and not change one into the other? Because MSYS's echo works finely

[bug #60435] Chained pattern rules with multiple targets not removing all intermediate files

URL: Summary: Chained pattern rules with multiple targets not removing all intermediate files Project: make Submitted by: None Submitted on: Thu 22 Apr 2021 02:00:49 AM UTC Severity:

[bug #60960] Fix/report race problem if having multiple "alias" for the same target

URL: Summary: Fix/report race problem if having multiple "alias" for the same target Project: make Submitted by: None Submitted on: Thu 22 Jul 2021 01:49:14 PM UTC Severity: 3 - Norma

[bug #61154] (w32/sub_proc.c) make_command_line should also quote full_exec_path.

URL: Summary: (w32/sub_proc.c) make_command_line should also quote full_exec_path. Project: make Submitted by: None Submitted on: Tue 14 Sep 2021 03:02:34 AM UTC Severity: 3 - Normal

<    1   2   3   4   5   6   7   8   >