1 |
Hi Raffaele, |
2 |
"Gentoo Cross Development Guide" is deprecated in favour of Gentoo Embedded |
3 |
project, which so far seems to suit my needs. I had a quick look on |
4 |
CodeSourcery's products a few days ago, but in freely available version they |
5 |
don't seem to offer me more than toolchain compiled with crossdev. Maybe I'm |
6 |
wrong and if I'll get stuck I'll give them a go. AFAIK the biggest |
7 |
disadvantage of crossdev-created toolchain, compared to other cross |
8 |
compilation tools, is that without usage of emulator (like qemu-user) it is |
9 |
not possible to compile things that use in their configure scipts checks |
10 |
that need to be run on the target architecture (like Perl). |
11 |
Sticking to arm-none-linux-gnueabi-emerge offers quite a lot of comfort so |
12 |
far, so I'll see where I can get. |
13 |
Thanks for your tips! |
14 |
|
15 |
Peter |
16 |
|
17 |
2011/10/14 Raffaele BELARDI <raffaele.belardi@××.com> |
18 |
|
19 |
> On 10/14/2011 01:14 PM, czernitko wrote: |
20 |
> > Hello! |
21 |
> > I started playing a little bit with cross compilation for ARM |
22 |
> > architecture. Using crossdev I created a toolchain for |
23 |
> > arm-none-linux-gnueabi tuple. |
24 |
> > Now I'd like to emerge some more packages, but perl constantly refuses |
25 |
> > to emerge and it is needed by many packages. |
26 |
> |
27 |
> Not a direct answer to your question, but I managed to cross-build a |
28 |
> functional linux rootfs (including X11/Xfbdev and QTEmbedded) for ARM |
29 |
> using buildroot. I found buildroot much easier to use than trying to |
30 |
> follow the now-deprecated "Gentoo Cross Development Guide". |
31 |
> Also, I used CodeSourcery's toolchain instead of building my own. |
32 |
> |