Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Reply-To: Cygwin List <cygwin AT cygwin DOT com>
Message-Id: <6.2.1.2.0.20050701114811.03d3eb08@pop.prospeed.net>
Date: Fri, 01 Jul 2005 11:51:07 -0400
To: Question NS <ns_questions AT yahoo DOT ca>, twall AT oculustech DOT com,
   cygwin AT cygwin DOT com
From: Larry Hall <lh-no-personal-replies-please AT cygwin DOT com>
Subject: Re: Qestion about Bash Fork Resource Temporily Unavailable More
In-Reply-To: <20050701092720.86869.qmail@web30101.mail.mud.yahoo.com>
References: <20050701092720 DOT 86869 DOT qmail AT web30101 DOT mail DOT mud DOT yahoo DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

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/