This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: cannot execute binary file
- From: Gerry Reno <greno at verizon dot net>
- To: cygwin at cygwin dot com
- Date: Tue, 17 Dec 2013 13:59:07 -0500
- Subject: Re: cannot execute binary file
- Authentication-results: sourceware.org; auth=none
- 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> <52B07B74 dot 7000802 at verizon dot net>
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