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:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=wxJVWF54Nqu0RFxykbNHgZMwMtkc7XKJaeMW3Avjg9X
	nHfpCEWBsiwyTVzmLpz1M0o2YSQOt+fXxH8Tqj5Hn4j7x54OZQNhy0jLRYDXAtYL
	teVWT3PxfEugFU3vY+wm5PAq/ahWLDbzWtrA4fwiUl+/05e+ZdSO8ahNckJhLYTc
	=
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:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=cW/ruIYHV+kRkHJuJqffHMjC7Yc=; b=QhNZWmzHNRPa+WCyy
	WkffXgW6qfTcaLbT27uPegCMLgKAp+aeJGCP9D6FCX/faOf+L00sspc0nKzTn9w1
	tP4BuxDUWCN+js+d/OazpiYTz29jz0f/XJDOvO1jM87oNOCtsik21eDfxQfXNPFw
	j70gdNOdJ52KPDomYUm0w9Ez2A=
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=AWL,BAYES_50,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2
X-HELO: vms173025pub.verizon.net
Message-id: <52B07B74.7000802@verizon.net>
Date: Tue, 17 Dec 2013 11:27:32 -0500
From: Gerry Reno <greno AT verizon DOT net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7
MIME-version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: cannot execute binary file
References: <52AF84E3 DOT 7070109 AT verizon DOT net> <52AF9A80 DOT 5010605 AT gmail DOT com> <52AF9B87 DOT 2030906 AT verizon DOT net> <52AFB969 DOT 6040501 AT cygwin DOT com> <52AFBDAE DOT 5040808 AT verizon DOT net> <1478338508 DOT 20131217133235 AT mtu-net DOT ru> <52B04744 DOT 1050108 AT aol DOT com>
In-reply-to: <52B04744.1050108@aol.com>
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7bit
X-IsSubscribed: yes

On 12/17/2013 07:44 AM, Tim Prince wrote:
>
> On 12/17/2013 4:32 AM, Andrey Repin wrote:
>> Greetings, Gerry Reno!
>>
>>> I just got finished installing Cygwin on another machine and this time the -c does work.  So I went back and looked at
>>> the original machine.  There are 2 cygwin installations on that machine in different directories. I had forgotten that
>>> Cygwin got installed a while back on this machine to support some app that needed it.  So somehow having 2 different
>>> installations breaks this mintty -e capability.  Does this qualify as a bug?  Is Cygwin supporting 2 independent
>>> installations?
>> It do support two _independent_ installations.
>> This means, each of them have no way to find out about existence of the other,
>> barring the full disk search.
>> Yours were not that independent. Likely, them both were listed in $PATH.
>>
>>
> This thread reminded me that I faced the similar problem.  Being lazy and not figuring out how to include the path to
> cygwin1.dll when running Intel VTune profiler, I copied the .dll to the existing PATH, thus breaking the installation
> when next running setup.
>

I checked the PATH and I don't see any cygwin1.dll on the PATH:

    C:\Documents and Settings\Administrator>which cygwin1.dll

    which: no cygwin1.dll in (.;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\W
    bem)



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