Bash mis-reports an executable file

Asked by tomdean

Ubuntu 11.10.
I copied some files from a FreeBSD system. Among them were some executables.
memByteTest.c and memByteTest, for example.

If I do
./memByteTest,
bash reports file not found.
ls -l shows executable permissions.
hd memByteTest will dump the file
objdump -d memByteTest will disassemble the file
file memByteTest shows 64-bit ELF (FreeBSD).

I realize memByteTest will not run on linux, but, bash should report unknown format, etc., anything but file not found!

Is there an update to bash, etc, that I missed?

tomdean

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu unity Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
tomdean (tomdean) said :
#1

I re-compiled memByteTest and it works. My question is not about running FreeBSD executables on Linux.

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#2

You may need to mark the file as executable using:

chmod +x memByteTest

You will NEED to be in the same folder as the file so that the command works.

Revision history for this message
tomdean (tomdean) said :
#3

YES, YES, I know all that. Please read my initial post.

Still, bash incorrectly reports file not found!

Can you help with this problem?

Provide an answer of your own, or ask tomdean for more information if necessary.

To post a message you must log in.