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=y1eDLWXWEUu4jZAK
	QrhI4bm43Ao4MEGWhqRSY8Ll/jJ2zTmnuQlHd35dyD8K6YorV+LtBvCnhUYjgGNJ
	IgPUMHKSvkRpVfivE6c8u3Rywr7Ee2wfbHXNHPFIF2/zsqm1nNPB9obqDZX2pD/U
	6Hq8UnEvo2jr8uNM5StS0Tg6HwQ=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <52B04744.1050108@aol.com>
Date: Tue, 17 Dec 2013 07:44:52 -0500
From: Tim Prince <n8tm@aol.com>
Reply-To: tprince@computer.org
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
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>
In-Reply-To: <1478338508.20131217133235@mtu-net.ru>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


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.

-- 
Tim Prince


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