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