X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 25 Mar 2009 10:29:28 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: [SOLVED] Re: under cygwin, zsh cannot run when built against ncurses9-5.7-13 Message-ID: <20090325142928.GC5286@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <49BF1770 DOT 9020007 AT gmail DOT com> <49C00B83 DOT 8050302 AT gmail DOT com> <20090317222721 DOT GB1505 AT ednor DOT casa DOT cgf DOT cx> <49C07781 DOT 1090702 AT gmail DOT com> <20090318053237 DOT GA31643 AT ednor DOT casa DOT cgf DOT cx> <49C09F09 DOT 3040804 AT gmail DOT com> <20090319103136 DOT GB26397 AT calimero DOT vinschen DOT de> <49CA2860 DOT 4090008 AT gmail DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49CA2860.4090008@gmail.com> User-Agent: Mutt/1.5.16 (2007-06-09) 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 On Wed, Mar 25, 2009 at 12:49:36PM +0000, Dave Korn wrote: > So the linker is DTRT, the problem has always existed but been masked by the >fact that nothing between -lm and -lcygwin used to import anything, the >problem has arisen now because now that does happen, and the solution is to >mung the symbols in the import top/tail sections in libm so that libm and >libcygwin both each add a complete import table entry of their own (there's no >problem having two import tables against the same DLL). Once I've figured out >how that perl script works, I'll be able to suggest a patch. Don't bother. I'll look into it. -- 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/