|
Just for testing purposes, I tried a static build from the aboriginal armv5l image, and it segfaults on my K1.
Now I will try the armv4tl (we already know armv4l works) image. Nope, that segfaults too.
It appears that ONLY the aboriginal arm4l dev-environment can build working K1 binaries, out of everything I tried (which is quite substantial).
One thing interesting is that the binaries from arm4l, arm4tl, and arm5l all report the same "file" info. And the build systems for all three report /proc/cpuinfo as arm5tej.
Now to use aboriginal armv4l to built an arm tcc that can run on the K1, eh?
|