<div dir="ltr">I was thinking to the same thing, but why don't let the neo's cpu collaborate? maybe with lower priority... i was thinking to mount the /usr/portage and /var/portage (where all the compiling take place) as network disk with nfs or something, and setting up distcc to compile first on the desktop and with less priority on the neo... could work, and you could have a complete system just by mounting a couple of netdisks..<br>
<br><div class="gmail_quote">On Tue, Sep 9, 2008 at 11:07 PM, Andreas Zuber <span dir="ltr"><zuber@puzzle.ch></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Am Dienstag 09 September 2008 18:45:09 schrieb Previdi Roberto:<br>
<div class="Ih2E3d">> Yes you can use gentoo with binary packages, but you loose the great<br>
> configurability given by the tuning of the USE flags... i think it's better<br>
> if i can manage to crosscompile from my desktop, and then copy the<br>
> generated binary on the moko. slower, but more flexible..<br>
<br>
</div>It may also be an option to configure DistCC for crosscompilation on your<br>
desktop. If you remove localhost from the list, everything will get compiled<br>
on your desktop and not on the freerunner. The difference is that you dont<br>
have to copy files and you can still use the USE flags. Hopefully :-)<br>
<br>
<a href="http://www.gentoo.org/doc/en/cross-compiling-distcc.xml" target="_blank">http://www.gentoo.org/doc/en/cross-compiling-distcc.xml</a><br>
<br>
I hope i get gentoo running on my Freerunner, so i can test this soon<br>
<br>
greetings<br>
Andy<br>
<div><div></div><div class="Wj3C7c"><br>
_______________________________________________<br>
Openmoko community mailing list<br>
<a href="mailto:community@lists.openmoko.org">community@lists.openmoko.org</a><br>
<a href="http://lists.openmoko.org/mailman/listinfo/community" target="_blank">http://lists.openmoko.org/mailman/listinfo/community</a><br>
</div></div></blockquote></div><br></div>