[bug #16362] Regression: make -n causes $(shell) failure on Windows
Follow-up Comment #1, bug #16362 (project make): Sounds like I should stop trying to maintain the Windows port, as I cause more trouble than help. ___ Reply to this item at: http://savannah.gnu.org/bugs/?func=detailitemitem_id=16362 ___ Message sent via/by Savannah http://savannah.gnu.org/ ___ Bug-make mailing list Bug-make@gnu.org http://lists.gnu.org/mailman/listinfo/bug-make
[bug #16362] Regression: make -n causes $(shell) failure on Windows
Follow-up Comment #2, bug #16362 (project make): Submitted by J David Bryan [EMAIL PROTECTED] Eli wrote, Sounds like I should stop trying to maintain the Windows port, as I cause more trouble than help. Seems a bit of a harsh judgment. In my view, the Windows port is in the best shape ever. To address the current problem, I see three alternative fixes: 1. Revert the patch so that batch files are always created, even with -n, and then add code to delete the files explicitly for the -n case around line 1125 of job.c. 2. Add an extra calling parameter to construct_command_argv to indicate whether the command will eventually be executed and so whether the batch file should be created (flag would be always true for the invocation via the shell function and conditional on -n otherwise). 3. Infer the type of call (shell function invocation vs. rule command invocation) from the values of the parameters and condition batch file creation on that and -n. I'm not crazy about (3), and I'm not sure which of the other two, if either, you'd find preferable. Also, I believe I've seen mention that job.c is undergoing renovations currently, so I'm loathe to select a repair method without advice. ___ Reply to this item at: http://savannah.gnu.org/bugs/?func=detailitemitem_id=16362 ___ Message sent via/by Savannah http://savannah.gnu.org/ ___ Bug-make mailing list Bug-make@gnu.org http://lists.gnu.org/mailman/listinfo/bug-make
[bug #105] Parallel builds should order by slowest-first
Follow-up Comment #3, bug #105 (project make): Closed support #105307 as a duplicate of this bug. See the details on that support request because it's slightly different, but any solution for this problem should ideally be hookable so that a generic re-ordering of prerequisites is possible. ___ Reply to this item at: http://savannah.gnu.org/bugs/?func=detailitemitem_id=105 ___ Message sent via/by Savannah http://savannah.gnu.org/ ___ Bug-make mailing list Bug-make@gnu.org http://lists.gnu.org/mailman/listinfo/bug-make
[bug #16372] .DELETE_ON_ERROR does not delete directories
URL: http://savannah.gnu.org/bugs/?func=detailitemitem_id=16372 Summary: .DELETE_ON_ERROR does not delete directories Project: make Submitted by: None Submitted on: Tuesday 04/18/06 at 18:44 UTC Severity: 3 - Normal Item Group: Bug Status: None Privacy: Public Assigned to: None Open/Closed: Open Component Version: 3.81 Operating System: Any Fixed Release: None ___ Details: As can be easily found out, either by a simple experiment or by reading the code in commands.c/delete_target, make does not even try to delete failed targets declared as prerequisites to .DELETE_ON_ERROR if they are not regular files. If this is desired behavior, the manual does not mention it. I argue that it is not desired. An application I am working on builds directories as target, and, for the reasons mentioned in the manual, leaving them hanging around after a failed build is confusing for the human, and produces wrong results for the program. The problem has been reported on the bug-make list as http://lists.gnu.org/archive/html/bug-make/2003-01/msg00014.html (receiving no replies). Bengt Martensson [EMAIL PROTECTED] ___ Reply to this item at: http://savannah.gnu.org/bugs/?func=detailitemitem_id=16372 ___ Message sent via/by Savannah http://savannah.gnu.org/ ___ Bug-make mailing list Bug-make@gnu.org http://lists.gnu.org/mailman/listinfo/bug-make
[bug #16376] command execution with make -q
URL: http://savannah.gnu.org/bugs/?func=detailitemitem_id=16376 Summary: command execution with make -q Project: make Submitted by: None Submitted on: 水曜日 2006年04月19日 at 01:04 UTC Severity: 3 - Normal Item Group: Bug Status: None Privacy: Public Assigned to: None Open/Closed: Open Component Version: 3.81 Operating System: POSIX-Based Fixed Release: None ___ Details: I find this behavior mysterious. Is this a bug or intentional? % cat Makefile Makefile: x @echo foo % make -q make: *** No rule to make target `x', needed by `Makefile'. Stop. % touch x % make -q foo ___ Reply to this item at: http://savannah.gnu.org/bugs/?func=detailitemitem_id=16376 ___ Message sent via/by Savannah http://savannah.gnu.org/ ___ Bug-make mailing list Bug-make@gnu.org http://lists.gnu.org/mailman/listinfo/bug-make
