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=DUTWLCwG7r1WFl0sBtwVbFSIqdrngf/xW5/StdKO0eY
	WUklBorwdKHi0ac2YFnWQSzxEmWnp9zI9ufJM9f39FcMdqYYHEnVrl/nIWu4WVVd
	6/ZK0btH4Kd8aHXIASN5t3OYi2RCA1mBGb2Ge0knwgwcsB5ZZI5/4PrZn9vRgt6o
	=
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=wdgMbZrvF1P52UqYYdpSAq2I8cA=; b=NyRIvdIbMQ+nXTECb
	CSaf/1ktuG2nwx0eLDiSCKy6TKUvkFr28A5kQ3IKV38U9sU+NRk5KWlST3+cI/c7
	vgpPnljtjU1309M1m3sc6ey1Y09lSNuHqbebUaAin8ysIltfSZUGyPGCv1FTGjtd
	/ZfrUti+iIAT2fXM/0OVhcGtkU=
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=-2.4 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2
X-HELO: vms173025pub.verizon.net
Message-id: <52AFBDAE.5040808@verizon.net>
Date: Mon, 16 Dec 2013 21:57:50 -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>
In-reply-to: <52AFB969.6040501@cygwin.com>
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7bit
X-IsSubscribed: yes

On 12/16/2013 09:39 PM, Larry Hall (Cygwin) wrote:
> On 12/16/2013 7:32 PM, Gerry Reno wrote:
>> On 12/16/2013 07:27 PM, Max Polk wrote:
>>> On 12/16/2013 5:55 PM, Gerry Reno wrote:
>>>>       /usr/bin/ls: /usr/bin/ls: cannot execute binary file
>>>>       /bin/bash: Exit 126
>>>>
>>>>
>>>> This is the error that greets me when I try to execute a command in cygwin from a Windows Command Prompt like so:
>>>>
>>>>       C:\cygwin\bin\mintty.exe -h always /bin/bash -l ls
>>>>
>>>> This was after installing a new version of Cygwin today.  So I wiped it and installed it again and got the same error
>>>> again.
>>>>
>>>> This used to work because I've called my own scripts this way before.  Is there some new way of doing this?
>>>>
>>>
>>> If you provide a "minus c" option, it will work:
>>>
>>> C:\cygwin\bin\mintty.exe -h always -e /bin/bash -l -c ls
>>>
>>
>> I just tried it with -c and all it gives you is a totally blank window.
>>
>> Tried a bunch of other commands using the -c and same thing.  Just a blank window.
>
> In that case, there's something in your installation that isn't quite right.
> The above suggestion resolves the issue you described just fine for me.  If
> you're still experiencing the problem when you use the '-c' flag and need to
> consult with the list further on this issue, I recommend following the
> problem reporting guidelines found at the link below with your next message:
>
>> Problem reports:       http://cygwin.com/problems.html
>
>

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?





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