[SOLVED] "command not found" but the file file exists!
UbuntuThis forum is for the discussion of Ubuntu Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
in such cases usually the first line of that file contains an interpreter, like here:
#!/path/to/interpreter
it is used to be /bin/bash, but in your case that file does not exists.
"arm-none-eabi-gcc" is a binary and the makefile doesnt need the #! but i even tried adding it to the beginning of the makefile, and the problem persists.
is it possible that the config of bash got corrupted somehow?
You are right, for makefiles the #! is not used although it would be possible.
You can check how the SHELL variable set. Which make have you tried? Also you can try if that file (/home/r1d3r/code/arm-2010q1/bin/arm-none-eabi-gcc) can be executed from the command line without make. Have you checked the permissions?
Is it executable? Is it the right binary format for the system you are trying to run it on? file arm-none-eabi-gcc would show what sort of binary it is. Is it named as it appears to be named? How does its full path look when listed with the --escape option of ls?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.