X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <4A644A13.4090507@gmail.com> Date: Mon, 20 Jul 2009 11:42:27 +0100 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: sh.exe: TP_NUM_W_BUFS too small? References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Magnus Holmgren wrote: > When running configure scripts, I sometimes see this error message repeated > several times, for different lines of the configure script: > > bin\sh.exe: *** fatal error - Internal error: TP_NUM_W_BUFS too small. > > I saw this when building libsdl 1.2.13 on Cygwin 1.7 (uname -v reports > 2009-07-13 10:28) on 64-bit Vista SP2. The configure script seem to have > succeeded anyway (the build completes and libsdl works). So, is it really > an error? Yes. Cygwin ran out of internal buffers for ASCII->Unicode conversion and the shell process was killed. This may not have caused you problems; configure will have interpreted it as meaning the autoconf test failed, so it maybe ended up thinking a certain header file or library wasn't present, and, depending which test it was testing at the time, that might have been the right answer anyway. cheers, DaveK -- 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