Error: *** fatal error - couldn't allocate heap, Win32 error 487

Windows CYGWIN Problems
Wrong make
There are some versions of CYGWIN make (/usr/bin/make.exe) that do not work with the drive letter paths. You need to get an older make.exe from say, http://www.cmake.org/files/cygwin/make.ex e ( join ex e = exe) and displace the /usr/bin/make.exe with this version.
CYGWIN can conflict with other windows software:
From time to time, people have reported strange failures and problems in Cygwin and Cygwin packages that seem to have no rational explanation. Among the most common symptoms they report are fork failures, memory leaks, and file access denied problems. These problems, when they have been traced, often appear to be caused by interference from other software installed on the same PC. Security software, in particular, such as anti-virus, anti-spyware, and firewall applications, often implements its functions by installing hooks into various parts of the system, including both the Explorer shell and the underlying kernel. Sometimes these hooks are not implemented in an entirely transparent fashion, and cause changes in the behaviour which affect the operation of other programs, such as Cygwin.
Among the software that has been found to cause difficulties are:
*
Sonic Solutions burning software containing DLA component
*
Norton/MacAffee/Symantec antivirus or antispyware
*
Logitech webcam software with "Logitech process monitor" service
*
Kerio, Agnitum or ZoneAlarm Personal Firewall
*
Iolo System Mechanic/AntiVirus/Firewall
*
LanDesk
*
Windows Defender
*
Embassy Trust Suite fingerprint reader software wxvault.dll
*
NOD32 Antivirus
*
ByteMobile laptop optimization client


Sometimes these problems can be worked around, by temporarily or partially disabling the offending software. For instance, it may be possible to disable on-access scanning in your antivirus, or configure it to ignore files under the Cygwin installation root. Often, unfortunately, this is not possible; even disabling the software may not work, since many applications that hook the operating system leave their hooks installed when disabled, and simply set them into what is intended to be a completely transparent pass-through mode. Sometimes this pass-through is not as transparent as all that, and the hooks still interfere with Cygwin; in these cases, it may be necessary to uninstall the software altogether to restore normal operation.