X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 	tests=AWL,BAYES_50,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <49C4E79E.3000005@cwilson.fastmail.fm>
Date: Sat, 21 Mar 2009 09:11:58 -0400
From: Charles Wilson <cygwin@cwilson.fastmail.fm>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.21) Gecko/20090302 Thunderbird/2.0.0.21 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: under cygwin, zsh cannot run when built against ncurses9-5.7-13
References: <20a807210903131414g62e0a53cyefd3938c3fe8af33@mail.gmail.com>   <49BADAC1.80709@cwilson.fastmail.fm> <gpf7kk$2g6$1@ger.gmane.org>   <gpfcdo$a30$1@ger.gmane.org> <gpgeu9$iuo$1@ger.gmane.org>  <Pine.LNX.4.64.0903142203230.9859@gremlin.fruitbat.org> <49BF1770.9020007@gmail.com> <Pine.LNX.4.64.0903202238560.16691@gremlin.fruitbat.org>
In-Reply-To: <Pine.LNX.4.64.0903202238560.16691@gremlin.fruitbat.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

Peter A. Castro wrote:

> True, the name does not fit the "current" naming convention for cygwin
> DLLs, but it doesn't really matter too much, since this particular DLL is
> private to zsh (it's really the core of zsh, which zsh.exe loads
> implicitly).  Since its an "internal" (to zsh) DLL and not useable by any
> other program I felt it was exempt from the naming "rules".  Is there a
> strong technical reason to rename it?  If so, I will do so.

I think the issue is, since zsh is built using libtool (right?) libtool
ought to DTRT.  Since it is not, it seems something is going wrong in
the build process; libtool doesn't "know" that it's supposed to be
building cygwin libraries.

So, what *else* is libtool doing wrong, as it happily runs through its
(linux? sun? sgi?)-specific code...

> BTW, good catch on the import libs being bad.  It's nice to know it's
> *not my fault, man!* :-)

Heh.

--
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/