I’m running into issues trying to execute a .run file on Centos 6.3. I have both Gnome & KDE installed and I’m booting to the KDE desktop. At first, the .run file wouldn’t even execute. Every time I tried to execute it I received “cannot execute a binary file”. I tried it running it from the CL & GUI Desktop. The CL tossed the previously stated error and the GUI did absolutely nothing. I’ve tried running it with “sh filename.run” * “./filename.run” with the same failed results.

I checked the file type with “file filename.run” and here’s what it returned: “ELF 32-bit LSB executable, Intel 80386, version 1 (GNU/Linux), statically linked, stripped”. I did some research and found that Centos is 64 bit and this executable is 32 bit. The post I read said I don’t have the 32 bit libraries installed so I installed them with “yum install glibc.i686” per the posters suggestion. When I run the file from the CL with “sh filename.run” I get the same “cannot execute a binary file” message. If I run it with “./filename.run” it does execute and prompts me for the installation information like the path and such, but the installation is not execute in GUI mode. It runs like a normal script providing prompts on the CL for input. The problem is that not all of the inputs are displayed to the user or prompted.

Now I know this installation will run in GUI mode because I tested it on an old 32-bit Centos 5.4 system I have and it runs fine and in GUI mode. I’m obviously missing some library or supporting Linux package and I’m hoping that someone can help me out.

If you run ldd on the binary file ("ldd /path/to/filename.run") it should tell you what libraries you are missing. Then it's just a matter of finding out what package provides those libraries.

Tried it. It returned "not a dynamic executable".

Sorry, I overlooked where you did say that the file command reported "statically linked." My guess at this point is that the program is doing its own check to see what GUI libraries are available. If the program does not have some option to report what it wants, all I can suggest is to use strace to see what library files it is looking for.Take a look at the resulting trace.out file and see what files with "lib" in the path the program is checking for.

2 members found this post helpful.