Michael S (already5chosen@yahoo.com) on 11/14/09 wrote:
---------------------------
>For me it's not even a link step which is most irritating but a make itself. Gnu
>make under cygwin absolutely horribly sucks!
>The one think I can not understand is how it manages to suck about equally on 3GHz
>Prescott with regular SATA drive and on 2.66 GHz Nehalem with two SATAs in RAID-0.

It's certainly because of fork() and friends. The implementation is incredibly inefficient, unfortunately it's the only way to do it on Windows and GNU/make makes plenty use of those calls. Wouldn't it be worth to give a try with virtualization? I'm currently using a Debian installation under VirtualBox which shares a few directories with my Windows installation so that it can work on them. With only one core of this system (very similar to yours) assigned to the VM it *flies* past Cygwin.

>I don't know whether VS2005 uses classic make for build management or some less
>generic technology but somehow it manages to work more than order of magnitude faster than gnu make under cygwin.

Yet I am bemused by the inherent sluggishness of VS2005 (& 2008) on a Nehalem system. A full build under Linux of a project of similar size is significantly faster. I wonder if I have mis-configured something.