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
t
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 install
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 for
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 wh
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
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 Win
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:
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
On 21/09/2012 08:53, Csaba Raduly wrote:
ls.exe is in the coreutils package. Try reinstalling that.
Out of curiosity, what is the output of
file /usr/bin/ls
Csaba
Thx for the replies. I ended up reinstalling the entire installation
because I'd managed to fill up the top-level directory w
On Fri, Sep 21, 2012 at 12:07 AM, RobF wrote:
> Seemingly spontaneously, my ls command has stopped working.
>
> $ ls
> -bash: /usr/bin/ls: cannot execute binary file
>
> I tried reinstalling bash and that didn't help. Any suggestions?
ls.exe is in the coreutils package. Try reinstalling that.
O
On 9/20/2012 6:07 PM, RobF wrote:
Seemingly spontaneously, my ls command has stopped working.
$ ls
-bash: /usr/bin/ls: cannot execute binary file
I tried reinstalling bash and that didn't help. Any suggestions?
Rob:
there could be any number of reasons "ls" won't run. U can't check the
On 11/2/2011 3:41 AM, Marco Atzeri wrote:
On 11/2/2011 9:10 AM, Edvardsen Kåre wrote:
Are there any debug options or logs to check when you get "cannot
execute binary file"?
Cheers,
Kåre
- if is it a permission problem you need to check the ACL permissions
see getfacl or ACL permission from
On 11/2/2011 9:10 AM, Edvardsen KÃre wrote:
>> Are there any debug options or logs to check when you get "cannot
>> execute binary file"?
>>
>> Cheers,
>> KÃre
>
> - if is it a permission problem you need to check the ACL permissions
> see getfacl or ACL permission from windows explorer
>
> - if
On 11/2/2011 9:10 AM, Edvardsen Kåre wrote:
Are there any debug options or logs to check when you get "cannot
execute binary file"?
Cheers,
Kåre
- if is it a permission problem you need to check the ACL permissions
see getfacl or ACL permission from windows explorer
- if you are missing dll
Are there any debug options or logs to check when you get "cannot
execute binary file"?
Cheers,
Kåre
On ti., 2011-11-01 at 13:00 +, Edvardsen Kåre wrote:
> On ti., 2011-11-01 at 07:28 -0500, Eliot Moss wrote:
> > On 11/1/2011 5:24 AM, Edvardsen Kåre wrote:
> > > I've built from source (gfort
On ti., 2011-11-01 at 07:28 -0500, Eliot Moss wrote:
> On 11/1/2011 5:24 AM, Edvardsen Kåre wrote:
> > I've built from source (gfortran) an application that won't run (cannot
> > execute binary file) and the "file" command prompts: PE32 executable
> > (console) Intel 80386, for MS Windows. (Yes, ch
On ti., 2011-11-01 at 07:28 -0500, Eliot Moss wrote:
> On 11/1/2011 5:24 AM, Edvardsen Kåre wrote:
> > I've built from source (gfortran) an application that won't run (cannot
> > execute binary file) and the "file" command prompts: PE32 executable
> > (console) Intel 80386, for MS Windows. (Yes, ch
Thx, very much. There are 2 files there exactly as you state.
Arun
Christopher Faylor wrote:
On Thu, Sep 07, 2006 at 07:19:39PM +0100, Dave Korn wrote:
On 07 September 2006 19:08, Arun Biyani wrote:
Recently, I've run into this "cannot execute binary file" problem. I
have not run this
On Thu, Sep 07, 2006 at 07:19:39PM +0100, Dave Korn wrote:
>On 07 September 2006 19:08, Arun Biyani wrote:
>>Recently, I've run into this "cannot execute binary file" problem. I
>>have not run this program for 3-4 months but before that it would run
>>fine in Cygwin. It was compiled and linked fo
On 07 September 2006 19:08, Arun Biyani wrote:
> Recently, I've run into this "cannot execute binary file" problem. I
> have not run this
> program for 3-4 months but before that it would run fine in Cygwin. It
> was compiled
> and linked for Cygwin even though "file" command says linux.
> [rom$:
20 matches
Mail list logo
