This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: fork: Resource temporarily unavailable errors after upgrading cygwin packages


On 12/30/2019 6:10 PM, David Finnie wrote:
> I recently upgraded my cygwin64 installation to get latest packages.
> 
> After the install, if I run a fairly lengthy GNU make with multiple concurrent 
> jobs (-j option) specified, some of the sub-makes fail with "Resource 
> temporarily unavailable" errors. In all cases, this has been when make is 
> starting a shell (i.e. $(shell ...) ) to help with setting up some of the 
> variables required in the make processing. The failure, however, occurs in 
> different places in the make files used (the make spawns several sub-makes).

Does this happen with every parallel make, or is it one specific program that 
you're building?  If the latter, can you give a detailed recipe so that others 
can try to reproduce the problem?

> Some example error output from make:
> 
> make[2]: ../../build/Make/platform_options.mk:9: fork: Resource temporarily 
> unavailable
> make[2]: ../../build/Make/platform_options_linux.mk:33: fork: Resource 
> temporarily unavailable
> make[2]: ../../build/Make/platform_options.mk:9: fork: Resource temporarily 
> unavailable
> make[2]: ../../build/Make/platform_options_linux.mk:33: fork: Resource 
> temporarily unavailable
> make[2]: ../../build/Make/platform_options_oss_l.mk:7: fork: Resource 
> temporarily unavailable
> make[2]: fork: Resource temporarily unavailable
> 
> Note that while some make operations fail as per above, the vast majority work - 
> including sub-makes that are executing the exact same lines that occasionally 
> fail. If I force make to run with 1 concurrent job (-j1), I don't get these errors.
> 
> I have confirmed via Windows Task Manager that the correct cygwin64 make and 
> bash are being invoked. The makefiles do not override the default SHELL.
> 
> I have tried all of the usual things:
> 
> - running rebaseall from ash (running as Administrator)
> 
> - using rebase-trigger full, and then re-running cygwin64 setup
> 
> - reverting to a slightly older version of make and bash

Have you tried reverting to cygwin-3.0.7-1?

> This all happened immediately after upgrading the cygwin installation, and I 
> didn't change anything else on my system in between make working perfectly, and 
> now consistently getting these errors.
> 
> Is anyone else experiencing this ? Does anyone have any further magic to try to 
> correct it ?
> 
> cygcheck.out attached.

The only thing that jumps out at me from your cygcheck output is that your PATH 
is very long.  I don't know if that's relevant, but you might try cutting it 
down before running make.

Ken

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]