X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: References: Date: Mon, 2 Mar 2009 10:26:43 -0500 Message-ID: <2bf229d30903020726q6287c0b9obd6f61d57ba44bac@mail.gmail.com> Subject: Re: [ANNOUNCEMENT] [1.7] Updated: {ncurses/libncurses-devel/ncurses-demo}-5.7-11; New: libncurses9-5.7-11 From: Chris Sutcliffe To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 > NOTE TO MAINTAINERS: You may need to add -ltinfo to LIBS when linking > against ncurses. Given that tgetent has moved to libtinfo, I've configured vim using: LIBS="-Wl,--enable-auto-import" ./configure --prefix=/usr \ --sysconfdir=/etc \ --libexecdir='$(sbindir)' \ --localstatedir=/var \ --datadir='$(prefix)/share' \ --mandir='$(prefix)/share/man' \ --enable-multibyte \ --without-x \ --enable-gui=no \ --with-features=huge \ --with-tlib=tinfo Building vim completes without error. However, when I try and execute the new vim.exe, I get: Vim: Caught deadly signal SEGV Vim: Finished. Segmentation fault Checking vim.exe: $ cygcheck src/vim.exe C:\cygwin-1.7\usr\src\vim\vim7\src\vim.exe C:\cygwin-1.7\bin\cygwin1.dll C:\WINDOWS\system32\ADVAPI32.DLL C:\WINDOWS\system32\ntdll.dll C:\WINDOWS\system32\KERNEL32.dll C:\WINDOWS\system32\RPCRT4.dll C:\WINDOWS\system32\Secur32.dll C:\cygwin-1.7\bin\cygtinfo-9.dll Is there something I'm missing? Chris -- Chris Sutcliffe http://emergedesktop.org -- 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/