|
I now have a mix of static and dynamic binaries in my k1_build folder, and when I chroot into it, some of the dynamics throw errors about missing or incompatible libraries. I really need a collection of all static arm binaries, but finding them is few and far between. I will need to build almost all tools from scratch it seems, just like everybody else seems to build either toolchains and/or complete root filesystems. And that is reported to take hours or days to build (depending on the speed of your desktop PC or target system). And yes, a lot of folks out there reported giving up on a chroot solution and reverted to building in their target system (just like folks here were/are building in K3 devices).
If building in a chroot on a desktop PC, it seems safest to just use a full static rootfs, so not fits and starts fighting will all the library incompatibilies with you import existing pre-compiled tools.
The windows folks have gone to extremes to assure backwards compatibility, but the linux folks just seem to think you will compile all your build tools (and/or root filesystems) from source for each project, it seems. Or so it seems...
|