I compiled again with the debian cross toolchain, arm-linux-gnueabihf-g++ testrpi.cpp -o file testrpi If using BeagleBone Black, BeagleBone Blue, BeagleBone AI or other board with on. If using an original BeagleBone or PocketBeagle, you are done. Insert SD card into your (powered-down) board, hold down the USER/BOOT button (if using Black) and apply power, either by the USB cable or 5V adapter. lib/ld-linux-armhf.so.3: No such file or qemu-arm-static -L /usr/arm-linux-gnueabihf/. Step 0.F: Boot your board off of the SD card. lib/ld-linux-armhf.so.3: No such file or qemu-arm-static -L /usr/arm-linux-gnueabihf/lib/. lib/ld-linux-armhf.so.3: No such file or qemu-arm-static. Testrpi: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, for GNU/Linux 2.6.26, BuildID=c9f6df786169d08d22cea6241eb584f062ab558c, not. (8) Produce the toolchain Create the directory /usr/local/xtools/ and change its owner to your user, so that Crosstool-ng can write to it. I compiled again with the linaro toolchain. In gdb options, enable the Cross gdb and Build a static gdbserver options the other options are not needed. Now I’m a little confused and honestly I lost overview and control. lib/ld-linux-armhf.so.3: Invalid ELF image for this architecture I tried a hard link but that didn’t solved but changed the sudo ln -s /lib/x86_64-linux-gnu/ld-2.23.so.
When i dynamically link it, I get the same error “/lib/ld-linux-armhf.so.3: No such file or directory”. ‘arm-linux-gnueabihf-g++ -static testrpi.cpp -o testrpi’ The Eclipse IDE is a multi-language integrated development environment which can be used to develop, install, and debug embedded applications. GDB allows you to stop and start a running program, examine its functioning, and make changes. When you compile with static linking it works for me. GDB, the GNU Project Debugger is a debugging tool provided with the GNU Compiler Collection (GCC). Hope I didn’t do major wrong things with that. That was not the case in the book so I deleted i386 with ‘sudo dpkg –remove-architecture i386’. When I did ‘dpkg –print-foreign-architectures’ i got: Is this another toolchain than the linaro? So, if we install the Debian Cross-Toolchain we leave the linaro-toolchain? I think so because of point 6 at page 280 of the book. Compiled my testrpi and ran it on the rpi