Mail Archives: cygwin/2006/09/07/14:50:13
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 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/
>
>
>
>
>
--
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/
- Raw text -