Re: [gentoo-user] Hoping someone can help explain distcc to me

[Matthew Finkel <matthew.finkel@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1640 bytes --]

On Sat, Aug 20, 2011 at 10:46 PM, Dale <rdalek1967@gmail.com> wrote:

> Peter Humphrey wrote:
>
>> On Sunday 21 August 2011 02:08:51 Paul Hartman wrote:
>>
>>
>>
>>> Could I just export the entire laptop - everything from the root
>>> directory and below - and chroot into that over the network? Then I
>>> wouldn't even need to emerge -k...
>>>
>>>
>> No, I tried that and got myself tied in knots - well, actually it was the
>> whole portage tree that I exported, not the entire system. I forget what
>> went wrong now, but it's definitely cleaner to tell the server to build
>> the
>> packages and the client to install from them. The emerge -k step is quick
>> too, and you have the advantage that you can see whether the packages are
>> actually there, unless you've switched colours off or not specified -v. (I
>> once found that they weren't there, which prompted me to go looking for
>> the
>> config problem. Like Dale, I'm quite a good tester!)
>>
>> You just have to make sure that the chroot is identical to the client.
>>
>>
>>
>
> Since you mentioned me.  I wish I could set up a quicky from my 4 core 64
> bit machine to compile 32 bit packages for a older 2GHz machine that belongs
> to a friend.  I was going to put Mandriva on it but the CD won;t boot up
> properly.  It stops at starting udev.  Grrrrr.
>
> How hard is it to set up a 64 bit machine to compile programs for a 32 bit
> system?
>
> Dale
>
> :-)  :-)
>
>
It's actually quite easy. IIRC, when I did it last, the only difference is
that when you chroot into the subsystem you need prefix the command with
linux32, e.g. linux32 chroot /path/to/chroot /bin/bash

[-- Attachment #2: Type: text/html, Size: 2262 bytes --]