Launch Failed. Binary not found. CDT on Eclipse Helios
I’m using Eclipse Helios on Ubuntu 10.04, and I’m trying to install CDT plugin on it. I download it from here here. And then I go to Install New Software and select the zip file (I don’t extract it, just select the zip file). And its ok, it installs, everything works fine, it shows optional features, blah blah blah. And then I create a new HelloWorld project. And when I try to run it, it shows an error and says: Launch failed. Binary not found. Can anyone explain me how to fix it? Thanks.
On MacOSX I had the same problem: after building the project it wouldn’t run and it gave me the message: «Launch failed. Binary not found.» I solved it by going to Run > Run Configurations. > C/C++ Application >
@PantelisSopasakis : I had this problem too, and solved in this way too. But even if the path still shows in the configuration, somehow I always had to go to the path and then click run instead of run as local c/c++ application . could u help?
@user2751691 I’m sorry, I can’t think of something (besides I’m currently not using MacOSX). Let me know how you solved it though if you find something.
@PantelisSopasakis : I solved it by changing the binary parser from elf parser to Mach O 64 parser. then it magically worked. Thanks.
Binary Parser ELF would be in Ubuntu / Linux. In mac your build binary parser should be Mach-O. See eclipse.org/forums/index.php/t/268200 I’ve added an answer
13 Answers 13
You must build an executable file before you can run it. So if you don’t “BUILD” your file, then it will not be able to link and load that object file, and hence it does not have the required binary numbers to execute.
So basically right click on the Project -> Build Project -> Run As Local C/C++ Application should do the trick
I built the project but it gives error even for #include
Although I followed this step but it was not working for me and the reason was, I didn’t save the file itself.
I don’t think this is the better answer. The problem could be because it was not built, a file was not saved, the incorrect parser was chosen. This only addresses one problem.
First you need to make sure that the project has been built. You can build a project with the hammer icon in the toolbar. You can choose to build either a Debug or Release version. If you cannot build the project then the problem is that you either don’t have a compiler installed or that the IDE does not find the compiler.
To see if you have a compiler installed in a Mac you can run the following command from the command line:
If you have it already installed (it gets installed when you install the XCode tools) you can see its location running:
If you were able to build the project but you still get the «binary not found» message then the issue might be that a default launch configuration is not being created for the project. In that case do this:
Right click project > Run As > Run Configurations. > Then create a new configuration under the «C/C++ Application» section > Enter the full path to the executable file (the file that was created in the build step and that will exist in either the Debug or Release folder). Your launch configuration should look like this:
executing binary file: file not found
I know there are similar questions out there, but I haven’t found a solution nor this exact case. The binary was built on Arch Linux using its GCC 4.7. The package works fine on the build system. The commands below were executed on:
Linux vbox-ubuntu 3.2.0-29-generic #46-Ubuntu SMP Fri Jul 27 17:03:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
The file in question is located here. It’s a Linux 64-bit to Windows 64-bit cross-compiler. Untarring it to ~/ gives a single ~/mingw64 directory which contains everything needed. When I try to run ~/mingw64/x86_64-w64-mingw32/bin/as this is what I get:
bash: /home/ruben/mingw64/x86_64-w64-mingw32/bin/as: No such file or directory /home/ruben/mingw64/x86_64-w64-mingw32/bin/as: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=0x0b8e50955e7919b76967bac042f49c5876804248, not stripped linux-vdso.so.1 => (0x00007fff3e367000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f2ceae7e000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f2ceaac1000) /lib/ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2 (0x00007f2ceb0a8000) I am truly at a loss. Any help is much appreciated. EDIT: Some more details: The build system is Arch Linux (currently glibc 2.16). The output of ls -l is:
-rwxr-xr-x 2 ruben users 1506464 11 aug 23:49 /home/ruben/mingw64/bin/x86_64-w64-mingw32-as Version References: required from libz.so.1: 0x0827e5c0 0x00 05 ZLIB_1.2.0 required from libc.so.6: 0x0d696917 0x00 06 GLIBC_2.7 0x06969194 0x00 04 GLIBC_2.14 0x0d696913 0x00 03 GLIBC_2.3 0x09691a75 0x00 02 GLIBC_2.2.5 linux-vdso.so.1 => (0x00007fff225ff000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007fd525c71000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fd5258b4000) /lib/ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2 (0x00007fd525e9b000) Version information: /home/ruben/mingw64/x86_64-w64-mingw32/bin/as: libz.so.1 (ZLIB_1.2.0) => /lib/x86_64-linux-gnu/libz.so.1 libc.so.6 (GLIBC_2.7) => /lib/x86_64-linux-gnu/libc.so.6 libc.so.6 (GLIBC_2.14) => /lib/x86_64-linux-gnu/libc.so.6 libc.so.6 (GLIBC_2.3) => /lib/x86_64-linux-gnu/libc.so.6 libc.so.6 (GLIBC_2.2.5) => /lib/x86_64-linux-gnu/libc.so.6 /lib/x86_64-linux-gnu/libz.so.1: libc.so.6 (GLIBC_2.3.4) => /lib/x86_64-linux-gnu/libc.so.6 libc.so.6 (GLIBC_2.4) => /lib/x86_64-linux-gnu/libc.so.6 libc.so.6 (GLIBC_2.2.5) => /lib/x86_64-linux-gnu/libc.so.6 /lib/x86_64-linux-gnu/libc.so.6: ld-linux-x86-64.so.2 (GLIBC_2.3) => /lib64/ld-linux-x86-64.so.2 ld-linux-x86-64.so.2 (GLIBC_PRIVATE) => /lib64/ld-linux-x86-64.so.2 The tested other OSes are Fedora 17 (glibc 2.15) and Ubuntu 12.04 (eglibc 2.15). Both zlib and glibc version requirements are met.
Cannot execute binaries in Ubuntu : file not found
When I try to run any executable file a file not found error occurs. Sometimes it says nothing but doesn’t do anything. For example, when I execute ./blah-blah.bin it fails finding the file when it is clearly there. When I execute ./blah-blah-file-2.sh , it is silent. Note 1: files have +x.
Note 2: root also cannot execute.
Note 3: everything from /usr/bin executes.
Note 4: I can’t try it from GUI, I have only access to its console. What’s the problem? Upd: suddenly some commands (e.g. ls ) begin fail with a file not found . They worked yesterday.
Please post the first couple of lines of that file (I’m betting it doesn’t contain the #! path to a valid shell).
./alfresco-install.bin: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.2.5, stripped
You wouldn’t happen to be trying to execute a 32bit binary on a 64bit OS without 32bit support packages? Without the ia32 libs you wouldn’t get very far on AMD64.
3 Answers 3
and check the output. This sounds suspiciously like it’s missing a dynamic library or two.
This solved my problem. I had the same issue where executing a file would just produce «not found» as if the file couldn’t be found. Using this I found out that it was trying to load a library that didn’t exists.
Check the mount options, specifically, whether it is mounted noexec.
If this is the problem, e.g. on /tmp, do
sudo mount -o remount,exec /tmp @Alexey: ahem.
Is it a script or a binary executable?
If it’s a script, check the #! line.
Depending on your shell, the error message for a command with a bad #! line can refer to the script rather than to the missing interpreter.
% cat foo #!/bin/no_such_interpreter echo hello % chmod +x foo % ./foo ./foo: Command not found. % Using bash, the error message is different:
$ chmod +x foo $ cat foo #!/bin/no_such_interpreter echo hello $ ./foo bash: ./foo: /bin/no_such_interpreter: bad interpreter: No such file or directory $ Even if the #! line looks ok, it can fail if there’s a \r character at the end of the line, which can often happen if the file was created on Windows. What does
head -1 blah-blah.bin | cat -A If that doesn’t solve the problem, show us exactly what command you typed and the error message that resulted.
EDIT : I realize your title suggests it’s a binary executable. Exactly what kind of file is it? What is the output of