| 1 |
> Christopher Friedt schrieb: |
| 2 |
> Yep that's where i actually got it |
| 3 |
>> If you absolutely need to compile it, then why don't you just set up a |
| 4 |
>> native compilation environment? Cross-compile gcc, portage, etc for |
| 5 |
>> armv4t, and any other dependencies of perl, and then boot the |
| 6 |
>> FreeRunner from your new kernel into a root filesystem that you've |
| 7 |
>> populated with all of the previous binary packages you've compiled. |
| 8 |
>> Then you should be able to 'emerge perl', although it will likely take |
| 9 |
>> |
| 10 |
> A long time? My guess is that it would take ages.... Well as i said i |
| 11 |
> emerged a binary package of perl and didn't bother myself with it any |
| 12 |
> more. It would be cool tho if it would be easier to cross-compile, but |
| 13 |
> what would life be without obstacles... |
| 14 |
|
| 15 |
At the moment i emerge packages on the freerunner because of the bad |
| 16 |
crosscompile support of most ebuilds. I installed distcc on the desktop pc |
| 17 |
to help during compilation. But the big problem is the configure script, |
| 18 |
it takes ages to complete. |
| 19 |
|
| 20 |
Someone came up with the idea to emerge the whole stuff in a |
| 21 |
qemu-freerunner. Does anyone already tried this? I wonder if it is faster |
| 22 |
than on the freerunner itself. |
Archives