Arm linux gcc no such file or directory

unable to execute ‘arm-linux-gnueabihf-gcc’: No such file or directory #42

Comments

RooHoo33 commented Oct 27, 2016

I run sudo python setup.py install and it comes back with the error unable to execute ‘arm-linux-gnueabihf-gcc’: No such file or directory`
Here is the full log: SteamController.txt

I am using a raspberry pi 3
Thanks

The text was updated successfully, but these errors were encountered:

ynsta commented Nov 2, 2016

I think you should install gcc-multilib.

On Fri, Oct 28, 2016 at 12:35 AM, RooHoo33 notifications@github.com wrote:

I run sudo python setup.py installand it comes back with the errorunable
to execute ‘arm-linux-gnueabihf-gcc’: No such file or directory`
Here is the full log: SteamController.txt
https://github.com/ynsta/steamcontroller/files/557174/SteamController.txt

I am using a raspberry pi 3
Thanks

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#42, or mute the thread
https://github.com/notifications/unsubscribe-auth/AB26C8lBW6NQCv0PpyBbP9FTb7xb8lQGks5q4Sc5gaJpZM4Ki5eD
.

RooHoo33 commented Nov 2, 2016

When I type sudo apt-get install gcc-multilib to install it I get Package ‘gcc-multilib’ has no installation candidate

waspbr commented Nov 26, 2016 •

I have the same issue with the Pie 3 running retropie. Apparently gcc-multilib is not in the repos.

Edit: The script seems to run well with python3

sudo python3 setup.py install

btyock commented Jan 3, 2017

I am also getting an error with arm-linux-gnueabihf-gcc as well as a few other things. I tried installing gcc-multilib and running it with python3 and neither are working.

Источник

gcc : directory : No such file or directory

I am trying to build the mali driver for linux 3.7 kernel from Here.

There is a separate build script like,

Actual host machine has 2.6 kernel, but im instructing make to use linux 3.7 kernel. The above make will call the Makefile of mali driver’s makefile.

For the above script, gcc version prints properly before and after make command, but when make entered in to kernel directory, gcc is not recognized.

it saying gcc : directory : No such file or directory.

same happens to arm-gcc too. Any Guess??

3 Answers 3

The problem is in drivers/gpu/vithar/ump/src/devicedrv/Makefile.common. It assumes that the vithar SDK has been pulled from SVN and has a valid SVN revision (it doesn’t).

You have 2 options: 1) Edit the file above to skip invocation of svnversion:

2) Add to make command line:

gcc is recognized, found, and executed. The error «gcc: directory: no such file or directory» is given by gcc itself.

For some reason, gcc is trying to access «directory» (i.e., an object called «directory»), which does not exist.

Maybe a wrong expansion or an unexpected environment variable.

Try checking the appropriate Makefile and your make command.

For example, if you issued a command such as

there is a risk that the system misinterpret KDIR , introducing two nonexistent objects «Kernel» and «directory» as well as an extra quotation mark. Such a possibility might explain the symptoms you observe. So, extra spaces in paths are definitely something worth checking.

Источник

cross compilation for ARM: error no such file or directory

I have written simple Hello world program and compiled it with gcc-arm-linux-gnueabi compiler. It compiles well but when i try to execute it on ARM machine it complains «no such file or directory». I think gcc-arm-linux-gnueabi is for embedded Linux only due to e(mbedded)abi . Is it different from ARM Linux ABI?

Please help me to solve this problem

When i execute this crosscomp on target ARM machine error is crosscomp no such file or dir

EDIT When I was using arm-linux-gnueabi-gcc the entry point was not matching with the target machine entry point (readelf -l crosscom) but when I compiled with aarch64-linux-gnu-gcc entry point matched with target machine. But now error becomes permission denied on ./crosscomp. I tried with sudo which says crosscomp: no such command.

1 Answer 1

How to identify the problem?

Contains something like:

and the problem is that that file does not exist on the target.

How to solve the problem?

Use a proper compiler, either:

• the person who created the disk image must provide you the cross compiler or tell you exactly how to build it, e.g. with crosstool-ng.
• compile your own image and cross compiler, e.g. with Buildroot. Here is an example.

use a native compiler on the target. But generally targets are much slower than your host, and space constrained, so you likely don’t want to do this.

You might also be able to use a functional emulator such as QEMU to build, and then only run the programs on a slower platform, e.g. gem5 or a slow board.

Just hacking up the interpreter is potentially not enough, notably you have to ensure binary compatibility between the program and the target libc, or program and kernel interfaces (syscalls, /proc , etc.) if you try to use -static (the target kernel might be too old and not contain the required interfaces). The only robust solution is to use the correct toolchain.

Источник

cross compilation for ARM: error no such file or directory/command not found

I have written simple Hello world program and compiled it with gcc-arm-linux-gnueabi compiler. It compiles well but when i try to execute it on ARM machine it complains «no such file or directory». I think gcc-arm-linux-gnueabi is for embedded Linux only due to e(mbedded)abi. Is it different from ARM Linux ABI?

Please help me to solve this problem

arm-linux-gnueabi-gcc -Wall -o crosscomp hello.c

When i execute this crosscomp on target ARM machine error is crosscomp no such file or dir

EDIT When I was using arm-linux-gnueabi-gcc the entry point was not matching with the target machine entry point (readelf -l crosscom) but when I compiled with aarch64-linux-gnu-gcc entry point matched with target machine. But now error becomes permission denied on ./crosscomp. I tried with sudo which says crosscomp: no such command.

The output of readelf is as below

1 Answer 1

This peculiar error message happens when the dynamic loader required by a particular executable is missing.

You can find out the name of the dynamic loader that you need by applying readelf to the problem executable. On my x86-64 Linux box, for example

(«program interpreter» is another name for «dynamic loader».)

So, run the above command on your crosscomp binary on your development box. (If you don’t have readelf or you get error messages, try arm-linux-gnueabi-readelf .) The file named after «program interpreter:» needs to exist on your target ARM machine. If you don’t know where to get it, please post the output of the above command + ls -l of the directory that should have the missing file in it.

Источник

gcc arm executable «no such file orr directory», wrong dynamic lib

I am trying to make a usable setup for gcc-linaro-arm-linux-gnueabihf-4.8-2013.11 on windows. Something happens at dynamic link:

The program compiles fine, but when deployed to ARM shows: «No such file or directory»

Searching the issue, seems that static build works but executable is huge:

Now I have a VisualGDB toolchain installed that builds (in IDE) with it’s own toolchain a similar executable (small, dynamic) that works so I guess this is nothing wrong with my ARM distribution.

Am I missing something or wrong include from gcc-linaro-arm-linux-gnueabihf-4.8-2013.11 ?

Thanks very much in advance,

One more investigation:

I run -readelf (for non working):

4 Answers 4

I solved by myself, thanks for support anyhow.

The cross-compiler from Linaro links with a new lib name (some name changes in Debian) such as /lib/ld-linux-armhf.so.3 but the BBB (default) distribution use a old name /lib/ld-linux.so.3. Both names should point (symlinks) on BBB to real used library which is ld-2.16.so

So create another symlink and that’s it.

Best regards and Merry Christmas to all,

/development/test.elf | grep lib /lib/ld-linux-armhf.so.3 libstdc++.so.6 libm.so.6 libgcc_s.so.1 libc.so.6 __libc_start_main)

It might well be a missing shared library on the deployment machine.

Try running $(CC)-readelf -d your-binary | grep NEEDED . This will display the names of the required shared libraries. Verify that they are present on the target machine

Try running ldd you-binary on the target machine. It should report what are the required dynamic libraries and if they have been found.

PS. Run the program on the target with strace your-binary . Look for open or access calls, which return error ENOENT .

I can think of the following as I had some similar issues before.

The arm distribution has the required libraries in a folder like /usr/lib or /lib in its distribution or some other folder and your compilation environment has these at a different location. If this is the case then either

• setting the library path using ld_library_path environment variable (or .bashrc) may help
• or creating the same folder structure as you have in your system may also help

I can see that your cross compilation does not take into account of any hardware specific libraries but it is just the new hardware’s system libraries it is going to be dependent.

Ofcourse I am assuming that you have done a chmod to make your program an executable in your arm hardware or emulator.

Источник