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