public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com
Subject: Re: Bash: Cannot execute binary file
Date: Tue, 29 Mar 2011 01:37:00 -0000	[thread overview]
Message-ID: <4D913667.9070006@cs.umass.edu> (raw)
In-Reply-To: <31263793.post@talk.nabble.com>

On 3/28/2011 8:27 PM, independentt wrote:
>
> Ok here is my problem I used to be able to run bIRCD on a shell before. But
> now first time I try cygwin, I WGET
> http://ircd.bircd.org/bewareircd-linux.tar.gz and unzip it, edit the config
> files. And now I try to execute it using (.) ./BIRCD and it says BASH:
> Cannot execute binary file. I have full access to the file and when I type
> file bircd it says ELF 32-bit LSB executable, Intel 80386, version 1
> (GNU/Linux), statically linked, stripped.
> I am a windowsx86 vista user

I could be off-base, but two quick thoughts:

1) Do the file permissions include x (executable) permission
as shown by ls -l?

2) Above you used ./BIRCD and bircd interchangeably for the names,
but in cygwin names can be case-sensitive. Have you tried the
case (upeer vs. lower) of the letters of the name exactly as
ls reports?

Best wishes -- Eliot Moss

--
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:[~2011-03-29  1:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29  1:34 independentt
2011-03-29  1:37 ` Eliot Moss [this message]
2011-03-29  1:42   ` independentt
2011-03-29  1:53     ` Eliot Moss
2011-03-29  1:38 ` Christopher Faylor
2011-03-29  2:28   ` independentt
2011-03-29  3:19     ` Christopher Faylor
2011-03-29  8:40       ` Eliot Moss
2011-03-29  9:12         ` Buchbinder, Barry (NIH/NIAID) [E]
2011-08-27  5:55           ` srinu
2011-08-27  8:08             ` Marco atzeri
2011-08-27  8:17             ` Jens Schweikhardt

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=4D913667.9070006@cs.umass.edu \
    --to=moss@cs.umass.edu \
    --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).