The version of gcc, binutils etc. that OpeniBoot expects are massively out of date. I had to fire up a Debian 8.7.0 VM and struggle through the apt package archives to get everything working. The OpeniBoot-toolchain (separate repo in the iDroid-Project org) can build on this version, using the host GCC 4.9.2 compiler. I don't know what difference there is between arm-elf-gcc, compiled by the OpeniBoot toolchain, and arm-none-eabi-gcc, which is provided by most modern Linux distros nowadays, but it turns out to be large enough that it won't actually work at all. When you try loadibec-ing it into a new device, it does nothing at all.
This post should serve more as a warning than anything for people who want to compile OpeniBoot in 2026.
The version of gcc, binutils etc. that OpeniBoot expects are massively out of date. I had to fire up a Debian 8.7.0 VM and struggle through the apt package archives to get everything working. The OpeniBoot-toolchain (separate repo in the iDroid-Project org) can build on this version, using the host GCC 4.9.2 compiler. I don't know what difference there is between arm-elf-gcc, compiled by the OpeniBoot toolchain, and arm-none-eabi-gcc, which is provided by most modern Linux distros nowadays, but it turns out to be large enough that it won't actually work at all. When you try loadibec-ing it into a new device, it does nothing at all.
This post should serve more as a warning than anything for people who want to compile OpeniBoot in 2026.