[geekmaster]

I successfully compiled working code for my K1, using aboriginal linux native compiling inside the Windows 10 x64 "windows subsystem for linux" (a feature only for microosoft "fast path" devs, available to everybody this summer). It is real Ubuntu Bash, without a linux kernel (and lots of missing syscalls in the translation layer). Thankfully, the aboriginal compile scripts launch their own linux kernel in qemu. And x86_64 bogomips are almost identical inside the emulated kernel as outside (native instruction set, with just a few percent CPU overhead for handling system faults). I did have to tweak Rob Landley's aboriginal scripts though, just so they could work in win10 bash.

BTW, with this latest win10 developer beta, you install bash just by typing "bash" at the command line. Even "apt-get install" works in it (though many apps get "Function not implemented" errors from all the missing syscalls). And no "binfmt" kernel module, so I built a simple script to simulate it. No workaround for the missing "chroot" though, but aboriginal x86_64 is an okay alternative for now, and it lets me run apps that fail in Win10x64 bash. I use "nc" to push tarballs both ways through the emulation shell between "inside aboriginal" and "outside in win10 bash" (until I get SMB or CIFS working in an aboriginal shell).

EDIT: And of course, like many embedded devices, the busybox/toybox implementation of "wget" lacks https:// support, and many source code repositories (like github, and many others) do not allow http:// access. So I need to use win10 bash "wget" with an "nc" pipe into my aboriginal shell. I need to compile a better "wget" for my aboriginal shells.