| 1 |
On Wed, Dec 17, 2014 at 9:31 AM, <meino.cramer@×××.de> wrote: |
| 2 |
> Matti Nykyri <matti.nykyri@×××.fi> [14-12-17 15:00]: |
| 3 |
>> > On Dec 17, 2014, at 14:13, Neil Bothwick <neil@××××××××××.uk> wrote: |
| 4 |
>> > |
| 5 |
>> > On Wed, 17 Dec 2014 10:52:44 +0100, meino.cramer@×××.de wrote: |
| 6 |
>> > |
| 7 |
>> >>>> Yes, thats it: First download all stuff THEN start compiling. |
| 8 |
>> |
| 9 |
>> 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. |
| 10 |
>> |
| 11 |
>> 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. |
| 12 |
>> |
| 13 |
>> > Another alternative would be to use a USB to ethernet adaptor on the |
| 14 |
>> > embedded board and connect it directory to your router. |
| 15 |
>> |
| 16 |
>> This also sounds good. Or setup server which has the usb and is always on. |
| 17 |
>> |
| 18 |
>> -- |
| 19 |
>> -Matti |
| 20 |
> |
| 21 |
> Hi Matti, |
| 22 |
> |
| 23 |
> thanks for your reply! :) |
| 24 |
> |
| 25 |
> crosscompiling is a pain. I tried several ways to do that (distcc was |
| 26 |
> among them) and it fails too often, for two reasons: Often the sources |
| 27 |
> are not prepared to be crosscompiled an include headers of my PC |
| 28 |
> (64bit) into the build of my ARM boards (32bit). Second reason: If the |
| 29 |
> crosscompilation needs meta-tools like moc for qt it fails too. The |
| 30 |
> time to fiddle out that mess is nothing what I have... ;) |
| 31 |
> |
| 32 |
> Ethernet over USB: |
| 33 |
> 1.) For each update I have to rearrange my setup here then. Back and |
| 34 |
> forth. Back and forth... |
| 35 |
> 2.) The DSL modem is running longer than needed. I dont like the idea |
| 36 |
> to have my internet connection running over such a long time |
| 37 |
> unattended. |
| 38 |
> |
| 39 |
> The problem must be solved in software. |
| 40 |
> |
| 41 |
> Best regards, |
| 42 |
> Meino |
| 43 |
|
| 44 |
The more common fix when dealing with that range of hardware is to |
| 45 |
build the packages on a more powerful system, then transfer them as |
| 46 |
binary packages. Doing so for arm board's a touch less trivial, but |
| 47 |
doable. This also solves the problem of fetching the same source |
| 48 |
packages repeatedly, if you share Distfiles between the build |
| 49 |
environments. I set up similar some time back based on these |
| 50 |
instructions: |
| 51 |
|
| 52 |
https://www.gentoo.org/proj/en/base/embedded/handbook/?part=1&chap=5 |
| 53 |
|
| 54 |
for a RasPI I was playing with and it worked pretty well. |
| 55 |
|
| 56 |
-- |
| 57 |
Poison [BLX] |
| 58 |
Joshua M. Murphy |
Archives