On Wed, Dec 17, 2014 at 9:31 AM, <meino.cra...@gmx.de> wrote: > Matti Nykyri <matti.nyk...@iki.fi> [14-12-17 15:00]: >> > On Dec 17, 2014, at 14:13, Neil Bothwick <n...@digimed.co.uk> wrote: >> > >> > On Wed, 17 Dec 2014 10:52:44 +0100, meino.cra...@gmx.de wrote: >> > >> >>>> Yes, thats it: First download all stuff THEN start compiling. >> >> If I were you, I would setup your pc to do cross-compiling of your arietta's >> packages and build them into binpkg's. This could be all stored on the pc >> and accessed via nfs for example. Then the first dependency calculation >> would be done on the pc to build the packages and the second on arietta >> using only binary packages. >> >> You should keep /etc/portage, /var/lib/portage and /usr/portage on the PC >> and not modifiable from the arietta. This way you only need to install the >> run time dependencies to the aritte. And install from bin pkg is really fast. >> >> > Another alternative would be to use a USB to ethernet adaptor on the >> > embedded board and connect it directory to your router. >> >> This also sounds good. Or setup server which has the usb and is always on. >> >> -- >> -Matti > > Hi Matti, > > thanks for your reply! :) > > crosscompiling is a pain. I tried several ways to do that (distcc was > among them) and it fails too often, for two reasons: Often the sources > are not prepared to be crosscompiled an include headers of my PC > (64bit) into the build of my ARM boards (32bit). Second reason: If the > crosscompilation needs meta-tools like moc for qt it fails too. The > time to fiddle out that mess is nothing what I have... ;) > > Ethernet over USB: > 1.) For each update I have to rearrange my setup here then. Back and > forth. Back and forth... > 2.) The DSL modem is running longer than needed. I dont like the idea > to have my internet connection running over such a long time > unattended. > > The problem must be solved in software. > > Best regards, > Meino
The more common fix when dealing with that range of hardware is to build the packages on a more powerful system, then transfer them as binary packages. Doing so for arm board's a touch less trivial, but doable. This also solves the problem of fetching the same source packages repeatedly, if you share Distfiles between the build environments. I set up similar some time back based on these instructions: https://www.gentoo.org/proj/en/base/embedded/handbook/?part=1&chap=5 for a RasPI I was playing with and it worked pretty well. -- Poison [BLX] Joshua M. Murphy
