Veetle_install_base64 cannot execute binary file

Skip to content. Star New issue. Jump to bottom. Copy link. I am seeing the same issue too on Raspberry Pi OS. Connecting to repo. HTTP request sent, awaiting response Maybe you can shed some light on how you do that? The only way that works for me extracted from here :. Use file 1 to determine.

If it is not a typo, as pointed out earlier, it could be wrong compiler options like compiling 64 bit under 32 bit. It must not be a toolchain. Or use directive ". I hope it helps. Sorry, for my english language. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. How to run binary file in Linux Ask Question. Asked 9 years, 10 months ago. Active 1 year, 5 months ago. Viewed k times. Improve this question. Mateusz Piotrowski 6, 9 9 gold badges 46 46 silver badges 74 74 bronze badges.

However, likely the generated binaries are for one reason or other Windows binaries. Also, if the program is public, you can post the link to the sources. Or just post the makefile here. Show 1 more comment. Active Oldest Votes. Improve this answer. This is the most common reason I've seen for this problem, using file will identify this quite quickly.

So there is no solution to this? You can not run Software for other Instruction set as native Programs. Add a comment. For Googlers: bit or bit? Check with file yourbinary Permission to execute? Ravan 8, 17 17 gold badges 55 55 silver badges 79 79 bronze badges. Onurhan Onurhan 71 1 1 silver badge 5 5 bronze badges. Mark Amery Mark Amery 1 1 gold badge 1 1 silver badge 12 12 bronze badges.

Michael Davidson Michael Davidson 1 1 bronze badge. Thank you for the link. I followed the instruction and got an error.

Can you help? Click to expand What does this. Give us some more details about the program you are trying to execute. It obviously needs some shared object but the last error message means that the binary format does not match. This is usually the case when there is a mismatch - an executable uses a library and they do not match binarily because they have not been compiled against each other for example, with different compiler options like calling convention or int size.