| 1 |
Hi Raffaele, |
| 2 |
how far did you get with compiling rootfs? Do you have complete gentoo |
| 3 |
installation including kernel compiled for ARM? Would it be possible to make |
| 4 |
vmdk/any other image for Qemu in which it could be run? I guess it would |
| 5 |
ease quite many things... |
| 6 |
|
| 7 |
As for my progress: I found out that patches from Cross directory does not |
| 8 |
work, but configure script has some options for cross compilation so I wrote |
| 9 |
ebuild with different parameters for perl Configure script. It assumes that |
| 10 |
you have ARM machine ready on network and with ssh daemon running - it uses |
| 11 |
ssh to transfer cross compiled binaries, run them remotely and uses the |
| 12 |
output to continue compiling on host pc. I had no problem with establishing |
| 13 |
that, but configure script still tries to run few binaries compiled for ARM |
| 14 |
on my x64 host machine. Fight continues! |
| 15 |
|
| 16 |
Stay tuned :) |
| 17 |
Peter |
| 18 |
|
| 19 |
2011/10/14 Raffaele BELARDI <raffaele.belardi@××.com> |
| 20 |
|
| 21 |
> On 10/14/2011 01:14 PM, czernitko wrote: |
| 22 |
> > Hello! |
| 23 |
> > I started playing a little bit with cross compilation for ARM |
| 24 |
> > architecture. Using crossdev I created a toolchain for |
| 25 |
> > arm-none-linux-gnueabi tuple. |
| 26 |
> > Now I'd like to emerge some more packages, but perl constantly refuses |
| 27 |
> > to emerge and it is needed by many packages. |
| 28 |
> |
| 29 |
> Not a direct answer to your question, but I managed to cross-build a |
| 30 |
> functional linux rootfs (including X11/Xfbdev and QTEmbedded) for ARM |
| 31 |
> using buildroot. I found buildroot much easier to use than trying to |
| 32 |
> follow the now-deprecated "Gentoo Cross Development Guide". |
| 33 |
> Also, I used CodeSourcery's toolchain instead of building my own. |
| 34 |
> |
Archives