[bug #64806] "invalid output sync mutex" on windows

2023-11-05 Thread Eli Zaretskii
Follow-up Comment #8, bug #64806 (project make): Is the brechtsanders build a 32-bit executable or a 64-bit executable? If it's a 64-bit executable, maybe the problem only rears its ugly head in a 64-bit build, because the ezwinports stuff is 32-bit. ___

[bug #64806] "invalid output sync mutex" on windows

2023-11-05 Thread Michael Davidsaver
Follow-up Comment #7, bug #64806 (project make): > This bug report lacks a reproduction recipe ... The closest which I think I can come to providing such a recipe is in WINE where "-Otarget -j" works with the ezwinports build, but not with the brechtsanders/winlibs_mingw build. detailed outputs

[bug #64806] "invalid output sync mutex" on windows

2023-11-05 Thread Michael Davidsaver
Follow-up Comment #6, bug #64806 (project make): > This bug report lacks a reproduction recipe ... Yes, I know. Unfortunately (well, in this instance ;) ) I run Linux exclusively on my personal systems and only interact with windows via continuous integration builds. Troubleshooting with CI is

[bug #64806] "invalid output sync mutex" on windows

2023-11-05 Thread Michael Davidsaver
Follow-up Comment #5, bug #64806 (project make): Quoting @shawnlaffan from https://github.com/StrawberryPerl/Perl-Dist-Strawberry/issues/148#issuecomment-1783929512 > The root cause of the issue seems to be that the make executables do not support recursive calls when they have been renamed. Call