public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Error in Cygwin 32 Bit in WIN 10 OS 64bit
Date: Thu, 29 Mar 2018 19:35:00 -0000	[thread overview]
Message-ID: <36f3fe92-efb2-88cb-6a18-6ea3e2585bce@gmail.com> (raw)
In-Reply-To: <CAMK4Ja+CksG-gUtzKtwZ2sLKwcNcw5-mSjoy53UeG=7tmZ8jOA@mail.gmail.com>

On 29/03/2018 08:02, SRI HARSHA Bulusu wrote:
> Hi,
> 
> 
> While running the build of software,i have encountered the following error
> 
> *[main] make 12276 E:\tools\cygwin\bin\make.exe: *** fatal error - couldn't
> allocate heap, Win32 error 487, base 0x1120000, top 0x1310000, reserve_size
> 2027520, allocsize 2031616, page_const 4096*
> 
> *1961286814 [main] make 19884 child_info::sync: wait failed, pid 12276,
> Win32 error 4390*
> 
> *1961330811 [main] make 19884 fork: child -1 - died waiting for longjmp
> before initialization, retry 0, exit code 0x1000000, errno 11*
> 
> *make[3]: module.mak : 89: fork: Resource temporarily unavailable*
> 

The first suggestion is to use the 64bit version of cygwin instead of 
the 32 bit; this reduce a lot the risk of fork failures.


As alternative, please provide the cygcheck.out
as mentioned on
> Problem reports:       http://cygwin.com/problems.html

I suspect you have too many packages installed

Regards
Marco

--
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

      parent reply	other threads:[~2018-03-29 19:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-29 16:30 SRI HARSHA Bulusu
2018-03-29 19:05 ` Brian Inglis
2018-03-29 19:35 ` Marco Atzeri [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=36f3fe92-efb2-88cb-6a18-6ea3e2585bce@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).