public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Larry Hall <lh-no-personal-replies-please@cygwin.com>
To: Question NS <ns_questions@yahoo.ca>,
	twall@oculustech.com,         cygwin@cygwin.com
Subject: Re: Qestion about Bash Fork Resource Temporily Unavailable More
Date: Fri, 01 Jul 2005 15:51:00 -0000	[thread overview]
Message-ID: <6.2.1.2.0.20050701114811.03d3eb08@pop.prospeed.net> (raw)
In-Reply-To: <20050701092720.86869.qmail@web30101.mail.mud.yahoo.com>

At 05:27 AM 7/1/2005, you wrote:
>checking which kind of 64-bit int to use... long long
>C:\CYGWIN\bin\sh.exe (62888): *** thread handle not
>set - 0x0<0x0>, Win32 error
>1450
>C:\CYGWIN\bin\sh.exe (62896): *** thread handle not
>set - 0x0<0x0>, Win32 error
>1450
>C:\CYGWIN\bin\sh.exe (62888): *** thread handle not
>set - 0x0<0x0>, Win32 error
>1450
>C:\CYGWIN\bin\sh.exe (62916): *** WFSO timed out after
>longjmp
>Signal 1
>./configure: Cannot fork: Resource temporarily
>unavailable
>./configure: Cannot fork: Resource temporarily
>unavailable
>./configure: Cannot fork: Resource temporarily
>unavailable
>./configure: Cannot fork: Resource temporarily
>unavailable
>tclcl-1.15 configuration failed! Exiting
>..../configure: Cannot fork: Resource t
>emporarily unavailable
>
>Your help is appreciated!

<snip>

Please read and follow the problem reporting guidelines at the link below:

>Problem reports:       http://cygwin.com/problems.html


Pay particular attention to the comment about *attaching* the cygcheck 
output.

At this point in time, without other info to go on, I'm going to suggest
you try the latest Cygwin package and, if that doesn't help, try the 
latest snapshot <http://cygwin.com/snapshots/>.

--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746                     


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

  reply	other threads:[~2005-07-01 15:51 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-01  9:27 Question NS
2005-07-01 15:51 ` Larry Hall [this message]
2005-07-01 19:07   ` Question NS
2005-07-01 20:47   ` Qestion about Bash Fork Resource Temporily Unavailable for NS2.28 and NS2.27 Question NS
2005-07-01 20:58     ` Brian Dessent
2005-07-03  3:56     ` Larry Hall
2005-07-03  3:59       ` daemon
2005-07-03  7:12       ` Question NS
2005-07-03 23:11         ` Larry Hall
2005-07-04  3:15           ` Question NS
2005-07-04 17:32             ` Larry Hall
2005-07-05  6:06               ` Question NS
2005-07-06  2:55                 ` Larry Hall
2005-07-06  6:28                   ` Question NS
2005-07-06 15:27                     ` Larry Hall
2005-07-08  3:29                       ` Yitzchak Scott-Thoennes
2005-07-08 14:12                         ` Larry Hall
2005-07-06 23:04                   ` Question NS
2005-07-07  2:48                     ` Larry Hall
2005-07-08  7:12                       ` Question NS
2005-07-08 13:54                         ` Larry Hall
2005-07-05  6:34               ` Question NS
2005-07-05  6:47               ` Question NS
2005-07-05  6:47               ` Question NS
2005-07-04  5:34           ` Yitzchak Scott-Thoennes
  -- strict thread matches above, loose matches on Subject: below --
2005-07-01  9:24 Qestion about Bash Fork Resource Temporily Unavailable More Question NS
2005-07-01 18:53 ` Brian Dessent

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=6.2.1.2.0.20050701114811.03d3eb08@pop.prospeed.net \
    --to=lh-no-personal-replies-please@cygwin.com \
    --cc=cygwin@cygwin.com \
    --cc=ns_questions@yahoo.ca \
    --cc=twall@oculustech.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).