From: Gerry Reno <greno@verizon.net>
To: cygwin@cygwin.com
Subject: Re: cannot execute binary file
Date: Tue, 17 Dec 2013 18:59:00 -0000 [thread overview]
Message-ID: <52B09EFB.5070004@verizon.net> (raw)
In-Reply-To: <52B07B74.7000802@verizon.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
next prev parent reply other threads:[~2013-12-17 18:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 22:55 Gerry Reno
2013-12-17 0:27 ` Max Polk
2013-12-17 0:32 ` Gerry Reno
2013-12-17 2:39 ` Larry Hall (Cygwin)
2013-12-17 2:58 ` Gerry Reno
2013-12-17 9:35 ` Andrey Repin
2013-12-17 12:44 ` Tim Prince
2013-12-17 16:27 ` Gerry Reno
2013-12-17 18:59 ` Gerry Reno [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-09-21 4:23 RobF
2012-09-21 7:54 ` P.Long
2012-09-21 8:27 ` Csaba Raduly
2012-09-21 13:06 ` RobF
2011-11-02 10:04 Edvardsen Kåre
2011-11-01 10:24 Edvardsen Kåre
[not found] ` <4EAFE5F0.7090404@cs.umass.edu>
2011-11-01 13:00 ` Edvardsen Kåre
2011-11-02 8:11 ` Edvardsen Kåre
2011-11-02 8:42 ` Marco Atzeri
2011-11-02 11:01 ` Eliot Moss
2011-11-01 14:32 ` Edvardsen Kåre
2006-09-07 18:08 Cannot " Arun Biyani
2006-09-07 18:19 ` Dave Korn
2006-09-07 18:27 ` Christopher Faylor
2006-09-07 18:50 ` Arun Biyani
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52B09EFB.5070004@verizon.net \
--to=greno@verizon.net \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).