Date: Thu, 7 Sep 2006 14:27:45 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Cannot execute binary file
Message-ID: <20060907182745.GB3831@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <45005FFE DOT 6030302 AT unix DOT telasic DOT com> <014301c6d2aa$2eb33e90$a501a8c0 AT CAM DOT ARTIMI DOT COM>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <014301c6d2aa$2eb33e90$a501a8c0@CAM.ARTIMI.COM>
User-Agent: Mutt/1.5.11
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT 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/