public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Cannot execute binary file
Date: Thu, 07 Sep 2006 18:27:00 -0000	[thread overview]
Message-ID: <20060907182745.GB3831@trixie.casa.cgf.cx> (raw)
In-Reply-To: <014301c6d2aa$2eb33e90$a501a8c0@CAM.ARTIMI.COM>

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 for Cygwin even though
>>"file" command says linux.
>
>>[rom$:553] m68k-elf-objcopy -O  binary  umon_rom.elf umon_rom.bin
>>/bin/m68k-elf-objcopy: /bin/m68k-elf-objcopy: cannot execute binary file
>>[rom$:554] file /bin/m68k-elf-objcopy
>>/bin/m68k-elf-objcopy: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.2.5, dynamically linked (uses shared libs), for GNU/Linux 2.2.5, stripped
>
>No.  No way on earth did it ever run that file.  If the file command
>says linux, then it IS linux.  You must have overwritten your cygwin
>version at some stage with a linux version.

I suspect that there is a m68k-elf-objcopy and a m68k-elf-objcopy.exe
file there.  The m68k-elf-objcopy (without the .exe extension) should be
deleted.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2006-09-07 18:27 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-07 18:08 Arun Biyani
2006-09-07 18:19 ` Dave Korn
2006-09-07 18:27   ` Christopher Faylor [this message]
2006-09-07 18:50     ` Arun Biyani
2011-11-01 10:24 cannot " 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
2011-11-02 10:04 Edvardsen Kåre
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
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

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=20060907182745.GB3831@trixie.casa.cgf.cx \
    --to=cgf-no-personal-reply-please@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).