[bug #46077] SHELL process handling does not work under Windows 10 in x64 build -> endless waiting

Follow-up Comment #4, bug #46077 (project make): Oh right, #43887 was indeed about a 64-bits (msvc) build. As sometimes my ez-make-4.1 builds hang with -j, I thought it could be because of this reason... but it could well be something else. I'll try to have a closer look by rebuilding 4.1-2 32-b

[bug #46077] SHELL process handling does not work under Windows 10 in x64 build -> endless waiting

Follow-up Comment #3, bug #46077 (project make): AFAIU, the problem only happens in a x86_64 build, so my 32-bit builds should be unaffected. Did I miss something? ___ Reply to this item at: _

[bug #46077] SHELL process handling does not work under Windows 10 in x64 build -> endless waiting

Follow-up Comment #2, bug #46077 (project make): Eli, I just saw that make-4.1-2-w32-src.zip from your ezwinports doesn't have that fix. Any chance for a 4.2pre build? ___ Reply to this item at: ___

[bug #46077] SHELL process handling does not work under Windows 10 in x64 build -> endless waiting

Update of bug #46077 (project make): Status:None => Fixed Open/Closed:Open => Closed Fixed Release:None => SCM Triage Status:

[bug #46013] Command overrides added to MAKEOVERRIDES are lost if there were no overrides in the command line

Follow-up Comment #2, bug #46013 (project make): I have a hard time seeing the relationship of Comment #1 with the bug report. I am not suggesting that override should automatically be passed on to submakes. It is precisely for this reason that I expect to be able to pass them on by way of change