X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <49BADAC1.80709@cwilson.fastmail.fm> Date: Fri, 13 Mar 2009 18:14:25 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.19) Gecko/20081209 Thunderbird/2.0.0.19 Mnenhy/0.7.6.666 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: under cygwin, zsh cannot run when built against ncurses9-5.7-13 References: <20a807210903131414g62e0a53cyefd3938c3fe8af33 AT mail DOT gmail DOT com> In-Reply-To: <20a807210903131414g62e0a53cyefd3938c3fe8af33@mail.gmail.com> 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 Vin Shelton wrote: > When I build the latest zsh sources on Cygwin 1.7 using > ncurses8-5.5.3, I get a working zsh. When I build the same zsh > sources against ncurses9-5.7-13, although the build completes > successfully, the executable will not run: > > $ /usr/local/zsh-2009-03-11/bin/zsh -f > $ echo $? > 127 > > My guess is that some kind of runtime dependency is missing, but: > > $ cygcheck /usr/local/zsh-2009-03-11/bin/zsh.exe > C:\cygwin\usr\local\zsh-2009-03-11\bin\zsh.exe > C:\cygwin\bin\cygwin1.dll > C:\WINDOWS\system32\ADVAPI32.DLL > C:\WINDOWS\system32\KERNEL32.dll > C:\WINDOWS\system32\ntdll.dll > C:\WINDOWS\system32\RPCRT4.dll > C:\WINDOWS\system32\Secur32.dll > C:\cygwin\usr\local\zsh-2009-03-11\bin\libzsh-4.3.9-dev-1.dll > C:\cygwin\bin\cygiconv-2.dll > C:\cygwin\bin\cygncurses-9.dll > C:\cygwin\bin\cyggcc_s-1.dll Just for grins, could you rebuild zsh against libncurses9 -- but this time use gcc3? cygiconv-2 and cygncurses-9 use the static gcc-3.4.4 libgcc.a, but you are apparently using the gcc-4.3.2 shared libgcc. I just wonder if that presents an incompatibility that could explain what you are seeing. -- Chuck -- 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/