[distcc] compiling with distcc on x86_64 from within a 32-bit chroot?

[Audio Phile]

How can I verify that my distro's gcc has a fully-qualified compiler name as you suggest?

--- On Sun, 6/26/11, Martin Pool <mbp at sourcefrog.net> wrote:

> From: Martin Pool <mbp at sourcefrog.net>
> Subject: Re: [distcc] compiling with distcc on x86_64 from within a 32-bit chroot?
> To: "Audio Phile" <da_audiophile at yahoo.com>
> Cc: distcc at lists.samba.org
> Date: Sunday, June 26, 2011, 1:23 PM
> Yeah, the other way is to make sure
> there is a fully-qualified
> compiler name (like gcc-linux-i386) that will work both
> inside the
> chroot (on the client) and outside (when invoked by distccd
> running
> outside on the server.)  On the server you probably
> want to make that
> name call into the schroot through a shell script, like I
> described
> above.
> 
> Martin
> 
> 
> 
> 
> On 26 June 2011 12:06, Audio Phile <da_audiophile at yahoo.com>
> wrote:
> > I think I have this solved.  I wrote up the steps on
> the Arch Wiki: https://wiki.archlinux.org/index.php/Distcc#Cross_Compiling_with_Distcc_in_a_Chroot
> >
> > In a nut shell, the strategy is to have two instances
> of distccd running (on different ports). One runs in the
> native x86_64 environment and the other in the x86 chroot.
> >
> > Is there a more elegant solution involving only one
> instance of distccd?
> >
> > --- On Sat, 6/25/11, Martin Pool <mbp at sourcefrog.net>
> wrote:
> >
> >> From: Martin Pool <mbp at sourcefrog.net>
> >> Subject: Re: [distcc] compiling with distcc on
> x86_64 from within a 32-bit chroot?
> >> To: "Audio Phile" <da_audiophile at yahoo.com>
> >> Cc: distcc at lists.samba.org
> >> Date: Saturday, June 25, 2011, 8:31 AM
> >> On 25 June 2011 05:22, Audio Phile
> >> <da_audiophile at yahoo.com>
> >> wrote:
> >> > Is this possible?  I have two x86_64 boxes
> both of
> >> which have 32-bit chroots for compiling.  I'm
> trying to get
> >> distcc to work INSIDE the chroots such that they
> can share
> >> processors.  I'm failing :)
> >> >
> >> > Basically, work doesn't get distributed
> outside of the
> >> chroot.  Has anyone done this and what was the
> trick?
> >>
> >> That should work fine.  You need to make sure
> it's the
> >> compiler inside
> >> the chroot that actually runs, for which there are
> at least
> >> two
> >> possibilites:
> >>
> >> 1- run distccd inside the chroot
> >> 2- if you need/want to run it outside, make sure
> that its
> >> path finds a
> >> shell script that runs 'exec schroot -c natty_32
> gcc "$@"'
> >> (adjust to
> >> fit) to enter the chroot
> >>
> >> m
> >>
> >
> >
>