X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=L+3W5/FF0bmKadUH
	f6aqqSEXTl6yt1gKxLqVSVEUGt7Xv4LR4Na4Dkf5eAgNHdAi5zlrE13t1lCZJbMj
	frVVPMNZRk1jhW6irjxpluos9NyI8slKAYbYGfJBDSsr+tY2yzpSnMD1T+1JaaLE
	aE+7jMCog8ywKJtVlGei9vSi/88=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=oHggXYmU0jmosnWmhen01i
	hkXhs=; b=QsX4flFbyet2Ky5zTBJ1Ynw5SqBySlPuhC91tovgEk+LmlLyIYZ2f3
	f+L/3qcT/GFlQDBrBW6Gomzod/7G2P40LJdgGXwAf421VP1GSxUkDCLtDdvUZSxZ
	iS2mzzYs4Rnru92/PK5ZvioTXWtqhl0nMTX45lRk1zjzyvEP1J+OM=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.1 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,KHOP_THREADED autolearn=ham version=3.3.2
X-HELO: vms173003pub.verizon.net
Message-id: <521B8A69.7020300@cygwin.com>
Date: Mon, 26 Aug 2013 13:03:37 -0400
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Reply-to: cygwin AT cygwin DOT com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Install problem with latest cygwin
References: <OF6A96FFA3 DOT C3ACBA3D-ON48257BD3 DOT 003026E5-48257BD3 DOT 0031E5E6 AT au1 DOT ibm DOT com> <521B79CC DOT 7040501 AT cygwin DOT com> <521B864B DOT 4070101 AT cornell DOT edu>
In-reply-to: <521B864B.4070101@cornell.edu>
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit

On 8/26/2013 12:46 PM, Ken Brown wrote:
> On 8/26/2013 11:52 AM, Larry Hall (Cygwin) wrote:
>> On 8/26/2013 5:05 AM, Allan Chandler wrote:
>>>
>>> I've been running CygWin on my Win7-64 laptop for some time and I
>>> recently
>>> decided to update to the latest packages, mainly because there's a bucket
>>> load more stuff in there.
>>>
>>> I renamed my cygwin directory to get it out of the way and downloaded/ran
>>> setup-x86.exe. Selected ALL packages for download with no install and let
>>> it run overnight.
>>>
>>> The following day, I ran setup again and opted to install from the local
>>> directory. This went well, right up to the post-install section where
>>> I got
>>> "Cannot locate cygncursesw-10.dll"-type dialog boxes for each of several
>>> dozen packages. I also get it when I try to run bash after exit.
>>>
>>> I had a look into the \cygwin directory where everything was created and
>>> there's no sign of this file (though it appears under my old version of
>>> CygWin in /bin). In the local package area where I downloaded everything,
>>> it appears to exist in the x86/release/Cygwin64/cygwin64-ncurses tar.bz2
>>> file but nowhere else in the package area is there a file even containing
>>> "ncur". So I'm wondering whether the fact that I'm running the x86
>>> installer means I don't get that file. In which case, why are the
>>> post-install scripts (and bash) trying to use it?
>>>
>>> Has anyone else manages to install the latest CygWin on Win7 this way?
>>> Can
>>> anyone offer some advice on getting it to work?
>>
>> Using the package search available at cygwin.com, it appears to me that
>> there has been a "hiccup" in the upload for this package.  Here are the
>> results of searching for cygncursesw-10.dll under x86 and x86_64:
>>
>> x86:
>>      x86/cygwin64-ncurses/cygwin64-ncurses-5.9-5
>>      x86/libncursesw10/libncursesw10-5.7-18
>>
>> x86_64:
>>      x86_64/cygwin32-ncurses/cygwin32-ncurses-5.7-1
>>      x86_64/libncursesw10/libncursesw10-5.9-4
>>      x86_64/ncurses-debuginfo/ncurses-debuginfo-5.9-4
>>
>> Note that the 64-bit version is also listed under the 32-bit
>> installation and vice-versa.  And this doesn't seem quite right.
>
> It's for cross-compiling, in case you want to build a 64-bit application
> under 32-bit Cygwin (and vice versa).

Ah, OK.  That makes sense then.  So then I guess these cross-compile
packages don't need the DLLs, right?

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

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