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/
