Quote:
Originally Posted by knc1
@geekmaster - first test - duplicate the above.
It is statically linked, it should run anywhere on the K1 that you put it.
copy /bin/busybox to ??? <wherever> you are trying to run your compiled code from (sd card, usb storage, whatever) -
then with that as the current working directory, do
./busybox
see if it will talk to you from that location on your K1.
I.E: We **know** this thing works, make sure it works for you also.
This first test is to eliminate any funky file system options that might be keeping your code from running properly (or at all).
|
I had no problem running K1 code in my qemu chroot. The problem is strictly inside the K1, where the only thing I can run is code built for the K1 (such as copied from /bin to /mnt/us, or from a firmware update rootfs), as I mentioned yesterday:
Quote:
Originally Posted by geekmaster
... And the ONLY binary code that runs on it is code I copied from the rootfs. Even static compiled code using the /lib copied from the K1 fails (either "not found", or segfault), as I mentioned previously. ...
|
Scripts run fine, and I have even successfully adapted some "eink animation" scripts of mine for the K1. I partially ported "titty" (tiny TTY emulator) but it does not display anything (yet) -- more to do.
Though code compiled with "lenny" libs in my qemu chroot runs in that chroot, code compiled using libs copied from the K1 fails in the chroot (and in the kindle). I really do want to run something custom on my K1, and not just stuff lab126 compiled for my K1...
And thanks for looking at the K1 file system. I am anxious to try something on my K1 that was compiled from outside lab126 (such as a "Hello World" program).