Re: [Mingw-msys] fork errors when running configure script

[Earnie B. <ear...@ya...>]

Infidel - wrote:
> 
> Hi again :)
> 
> When I try to build libstdc++ (a recent snapshot), I get the following error
> in 'configure':
> 
>       0 [main] sh 1596067 fork_copy: user/cygwin data pass 2 failed,
> 0x9E0000..0xBE8000, done 0, windows pid 4294446449, Win32 error 8
> /devl/gcc/libstdc++-v3/configure: fork: Resource temporarily unavailable
>       0 [main] sh 1580019 fork_copy: user/cygwin data pass 2 failed,
> 0x9E0000..0xBE8000, done 0, windows pid 4294609041, Win32 error 8
> /devl/gcc/libstdc++-v3/configure: fork: Resource temporarily unavailable
> 100446 [main] sh 1580019 fork_copy: user/cygwin data pass 2 failed,
> 0x9E0000..0xBE8000, done 0, windows pid 4293348361, Win32 error 8
> /devl/gcc/libstdc++-v3/configure: fork: Resource temporarily unavailable
> make: *** [configure-target-libstdc++-v3] Error 1
> 
> I am using MSYS 1.0.6 with DLL snapshot 20020402 on Windows 98, a Celeron
> 333 with 96 MB RAM. I have the same result running from rxvt or from just
> sh.
> 

Unfortunately, I don't have a Win98 machine available to test this.

> The error happens a long way into the configure script, but at a different
> place each time I have tried it. This, and the "Win32 error 8"
> (ERROR_NOT_ENOUGH_MEMORY) might suggest that virtual memory is simply
> running out, since the script has 20K+ lines.
> 
> However, if I look at the total memory usage in System Monitor, there is
> very little change during execution of the script, and the swapfile only
> reaches about 120 MB. After I get this error, I am returned to the sh
> prompt, but if I then try to run any Windows console program, I get an error
> from Windows that there is not enough memory. On the other hand, I CAN run
> ANY Windows GUI program (e.g. IE 5), and Resource Meter reports 68% system
> resources free.
> 

IIRC, w9x has always provided unique challenges w.r.t. your reported
problem AFA Cygwin is concerned.  Since Cygwin is the code base then
those same challenges exist for MSYS.

> Also, I did not have this problem on a different computer running Windows
> 2000, though that system also has more memory.
> 

My build/test equipment is NT4 SP5 and SP6, so it's not surprising that
you don't have problems with Windows 2000.  I'm not going to be able to
help right away with this.  I'm looking over the Cygwin patches between
1.3.3 (the version MSYS is based on) and 1.3.10 (the current published
Cygwin version).  Perhaps some of those changes may be relevant. 
Anyway, thanks for the report.

> BTW, Sorry if I am becoming a nuisance :-)
> 

Anyone who supplies patches isn't ever nuisance. :)

Earnie.
P.S.: Don't bother with the snapshot yet.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com