How to execute .x86 binary file?

[bg3075]

I found a Linux .x86 binary file that I've been looking for, but not sure what to do with it. Does this (*.x86) binary file format seem like something that could simply be run by command, or something that would need to be compiled first? There is not much information that I could find regarding the particularly file.

[Hlingler]

Please state exact name of file.

Most binary executables (*.bin, *.run) can be run from CLI from folder where located so:
$ cd Downloads
$ su
# sh ./VirtualBox-3.2.8-64453-Linux_x86.run

Sometimes you must make the file executable first:
# chmod +x VirtualBox-3.2.8-64453-Linux_x86.run

This all assumes a 32-bit OS for a 32-bit executable.

V

[bg3075]

Yes, I too am familiar with those binary file types. This one, as is, was "rq-sssp-client.x86". I have never seen a binary file with .x86 extension.

[Hlingler]

I would simply [attempt to] execute it as shown above. Chances are it will fly. You could find out more by:
$ file rq-sssp-client.x86

I would expect the result to be: 'Bourne shell script text executable'

If instead it's an actual ELF binary, then double-click in file manager will open it.

I have never seen a binary file with .x86 extension.

They do seem to be rare, but I have seen them:
$ locate .x86
/usr/local/games/Loki_Demos/demos/civctp_demo/civctp_demo.x86
/usr/local/games/Loki_Demos/demos/heretic2_demo/heretic2_demo.x86
/usr/local/games/Loki_Demos/demos/heroes3_demo/heroes3_demo.x86
/usr/local/games/Loki_Demos/demos/myth2_demo/myth2_demo.x86
/usr/local/games/Loki_Demos/demos/rune_demo/rune_demo.x86

The above are mostly ELF compiled binary executables; one is an executable shell script; all can be opened from file manager (or from CLI as stated if a shell script).

V

[bg3075]

Results:

$ file rq-sssp-client.x86
rq-sssp-client.x86: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.4.1, stripped

It does nothing when executing from double-click in file manager. From command returns:

$ rq-sssp-client.x86
bash: rq-sssp-client.x86: command not found

[Hlingler]

Since it's an ELF binary, omit 'sh' and use full PATH or PATH locator as shown above:
$ ./rq-sssp-client.x86

This assumes that you are in the folder where the target file resides. This app may also require elevated privileges.

It does nothing when executing from double-click in file manager.

Hmm... it should run. Perhaps it's not flagged as executable (see 'chmod' above), or requires elevated privileges.

V

[bg3075]

Yes,

./rq-sssp-client.x86

appears to work, as for the program.

Now, how to find out the Linux port name for "Com1" Windows equivalent?

Thanks

[Hlingler]

I would recommend that you start a new thread to ask that question: I have no idea, and those members who do may overlook the question since it's buried at the end of a thread with unrelated title.

Glad it worked.

Good Luck,
V

[bg3075]

Right... thanks, Hlingler!

OK, got that...COM1 = ttyS0

But, now it is giving a segmentation fault.

[forkbomb]

Originally Posted by bg3075

Right... thanks, Hlingler!

OK, got that...COM1 = ttyS0

But, now it is giving a segmentation fault.

Is it third party software not obtained from Fedora repositories? I'm guessing if you're seeing third-party software segfault, the first place to ask would be the vendor of that software or any forums for that software. Not so sure that's a specifically Fedora-related issue, unless for some reason it doesn't like the device node you'e giving it (and /dev/ttyS0 is generally the first serial device).

You could try

ls /dev/ttyS*

and try any outputted device nodes instead of ttyS0. You'll probably see at least a few -perhaps 4 - even on a box without serial ports.

[stevea]

It's a really bad idea for the software distributor to ship a dynamically linked binary - like yours - without also shipping all the libraries. Libraries change revisions all the time and become incompatible,

Try the command
ldd ./rq-sssp-client.x86
and post the results. The "ldd" command will list the libraies requires and *if present* their location.

[bg3075]

Originally Posted by stevea

It's a really bad idea for the software distributor to ship a dynamically linked binary - like yours - without also shipping all the libraries. Libraries change revisions all the time and become incompatible,

Try the command
ldd ./rq-sssp-client.x86
and post the results. The "ldd" command will list the libraies requires and *if present* their location.

Here are the results:

# ldd ./rq-sssp-client.x86
	linux-gate.so.1 =>  (0x00da9000)
	libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00b0b000)
	libm.so.6 => /lib/libm.so.6 (0x004c8000)
	libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00876000)
	libc.so.6 => /lib/libc.so.6 (0x00350000)
	/lib/ld-linux.so.2 (0x0032e000)

---------- Post added at 03:22 PM CDT ---------- Previous post was at 03:07 PM CDT ----------

The program I have, "rq-sssp-client.x86" is supposed to sit idle, waiting for a request from the serial device. Is there a Linux command to have it wait for device request?