[Xastir] Cygwin

[Huller Gyula]

Thank you Henk and Curt, you were right. The 128 MB ram is not enough. 
During 1 whole night make finished the compilation and I got xastir.exe. 
Now it is fine.

73 and tnx!

Gyuszi - ha2vr

PS: Curt, I do not know what was the problem earlier but now com 
detection is OK without applying the changes you informed me last time. 
Win2k. Xastir source: as it is from cvs



Curt Mills wrote:

>On Sat, 3 Apr 2004, Henk de Groot wrote:
>
>  
>
>>I get the same GCC error as you have. Linking takes a while, eating a lot
>>of RAM for this task, but it does produce a correctly linked Xastir. I
>>think you have to be patient, if your swap file grows then you may not have
>>enough memory and that will slow down this step a lot more. Eventually it
>>should succeed however. I have 512 MB on this machine with an Athlon XP3000+.
>>    
>>
>
>On one Win2k machine I tried Cygwin/Xastir on, it had 128MB physical
>RAM.  With the normal things that were running on the machine,
>including virus scanning and such, it had very little left.  The
>final link step of the Xastir compile would try over and over to
>complete, but would run out of RAM.  That step kept trying for a day
>and never completed.
>
>The fix was to install more RAM in that system.  The system had
>recently been upgraded from WinNT4 to Win2k, and the 128MB just
>wasn't enough for it anymore.  Not with all of the other things that
>were required to be running in that environment anyway.
>
>  
>