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=BCxeTJAFOC2WqLyVoIjTVo/rwLgqmEEFphw4fwqKG7h
	EKfb7iAkt+VP5t1GXU8q5GUV159xZepmY+DiRPxhtN+er6X73G0MK92nDFkD/r/S
	A/S61wbxQe6C3QtwqiJ71ntXuwczsr8weSlapC8V/zhTVgkSKgU5hQmeopMgeu2c
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-id: <52B09EFB.5070004@verizon.net>
Date: Tue, 17 Dec 2013 13:59:07 -0500
From: Gerry Reno <greno@verizon.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@cygwin.com
Subject: Re: cannot execute binary file
References: <52AF84E3.7070109@verizon.net> <52AF9A80.5010605@gmail.com> <52AF9B87.2030906@verizon.net> <52AFB969.6040501@cygwin.com> <52AFBDAE.5040808@verizon.net> <1478338508.20131217133235@mtu-net.ru> <52B04744.1050108@aol.com> <52B07B74.7000802@verizon.net>
In-reply-to: <52B07B74.7000802@verizon.net>
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7bit

On 12/17/2013 11:27 AM, Gerry Reno wrote:
> 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)
>
>
>
>
I went and wiped BOTH of these Cygwin installations off the machine and went and installed 2 new installations in the
same directory locations and now both installations work when invoking mintty -e.  So it might have been that one of the
installations was much older and was causing some problem with independent installations.


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