Philip Heron wrote:
Lennert Buytenhek wrote:
> The simple approach would be to just take all SRPMS in the f8/f9
> distro, and do "rpmbuild --target armv4l foobar.src.rpm" for each of
I tried this with some core packages over the weekend, enough to chroot
into and play around with. The resulting environment works in qemu, but
when I copied the chroot over to the phone it give me an Illegal
Instruction error. Seems some armv5 code has sneaked in - possibly
through static linking - I don't know.
Another Aussie did some work on the arm4/arm5 problem to try and get
Android working on the Neo 1973:
He is obviously more clued-up than I am about this low level stuff - I
asked him if he had any experience with Fedora but he said no and
thought that: "I would probably start looking at something like
PokyLinux, or one of the embedded Linux distros."
"Well, the important thing here is that you want simply need to
recompile the kernel, but all the user application as well. This is the
problem I ran into with Android, recompiling the kernel is the easy bit,
it is the applications which will kill you."
I suppose the solution could be to rebuild these packages within the
chroot, but I don't have nearly enough armv4 packages built for this. A
job for Koji?
> Actually, I think Dennis has set up a koji instance for ARM, so if you
> want to try to use this to rebuild f8 for armv4l, that would probably
> be a good test of the system. And it should dramatically reduce the
> amount of work you'll need to do to get an ARMv4 Fedora up and running.
Would there be much work involved in getting this up and running?
I had a look at:
and installed koji - it seems I need to do something like:
koji build dist-fc7-scratch
I would need to be able to build a kernel/boot image and then come back
to the root image?
GPO Box 3411
Sydney NSW 2001