Quote:
Originally Posted by donB006
DId you get the K1 rootfs image unsquashed? Did you find the remaining files in /usr/default someplace and get those added to your K1 copy for a complete system? That should allow you to chroot into the virtual K1 and run your actual K1 programs except with the modern kernel imitating a K1 kernel. That is as far as I got.
|
I could not unsquashfs in my linux mint 17 because it says unsquashfs not installed, but I can do "apt-get install squash-tools" to get it. I tried that, but like so many other things in mint 17, apt-get reports "deprecated or not found". Synaptic Package manager also cannot find it. So no, no extraction (except on Win32 7-zip, to NTFS).
However, no luck finding out how to config aboriginal to built ucLibc with those missing symbols. The only place found is in "automatically generated, do not edit" files. And no "configure" script either, but a wrapper C program (he says uclibc config broken). No obvious way to set those flags in a re-generated file...
Studying the scripts DID lead me to armv4l cross-tools that work on x86 linux, built as an intermediate stage needed in a full aboriginal build. He says to only use them on distcc hosts. He says to build target apps in the qemu emulated custom kernel and rootfs only (for maximum target compatibility, especially for complex builds).
Despite those warnings, I used the "not for general use" crosstools in x86 linux to compile a "Hello World" that ran fine on my K1. If that fails on a complex build, I can fall back to his recommended "fully encapsulated" build environment. The crosstools are at least 10x faster (but it feels like 100x). Though again, elsewhere in the docs, he suggests that to use cross-tools, you should use these primitive cross tools to build better more robust cross-tools (these used crude hacks to override hard-coded paths in the host gcc that built them).
So at least that is another option. What I already did instead of unsquashfs is to untar the tarballs of my K1 rootfs (from the device, not the update package), so that problem can be side-stepped for now...