Please choose just one GNU make mailing list to ask questions on: it gets confusing if multiple lists are involved.
On Mon, 2017-06-05 at 11:08 +0000, Ramya S Ganesh (RBEI/ETC5) wrote: > We tried executing make scripts using 4.1 version of make in Windows > 7 PC and it took a reasonable amount of time. Whereas when we tried > executing the same scripts with the same version of make in Windows > 10 PC, the time taken was enormous. Why do you believe that the difference in time taken was due to make itself, and not the scripts that make is invoking and whatever operations they perform taking longer on Windows 10? If you run the scripts by hand from the command line instead of through make, do they work at the same speed on Windows 7 and Windows 10? > Do you have any idea what might be the reason for this delayed > execution in Windows 10? I have no idea; you'll need to provide much more information before we could even begin to guess. We'd need to know how you are invoking make (are you using parallelism (-j)? Synchronized output? Other options?) Likely you will need to run make with debugging enabled (the -d option, but keep the output as it will be voluminous) and see if you can detect any difference in output between the different versions of Windows. Offhand I'm skeptical that the problem is related to make; more likely it's some other aspect of the system that has changed between Windows 7 and Windows 10. _______________________________________________ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make
