public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: cannot execute binary file
Date: Tue, 17 Dec 2013 02:39:00 -0000	[thread overview]
Message-ID: <52AFB969.6040501@cygwin.com> (raw)
In-Reply-To: <52AF9B87.2030906@verizon.net>

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


-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

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

  reply	other threads:[~2013-12-17  2:39 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) [this message]
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
  -- 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=52AFB969.6040501@cygwin.com \
    --to=reply-to-list-only-lh@cygwin.com \
    --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).