Bugzilla Bug 120076

I came up with a very easy method for seamless cross-compiling with distcc.
It's described in <http://www.gentoo.org/doc/en/cross-compiling-distcc.xml>.
I've put together a patch to automatically perform these steps when the user
wants to use distcc with catalyst.

Created an attachment (id=77926) [details]
automatically sets up cross-distcc-fu

This is against catalyst-2.0_rc20, but the changes are localized so easy to put
into any version.

Created an attachment (id=77998) [details]
new patch that uses single quotes instead of double quotes to create the
wrapper

I'm currently running an amd64 stage1 build with this patch. It is distributing
properly to the sparc.

Created an attachment (id=78003) [details]
new (hopefully) working patch

When I switched to single quotes in the last patch, it killed the ${CHOST}
substitution when writing out the wrapper script. This should fix that.

Created an attachment (id=78029) [details]
slightly different approach to wrapper script

I just finished a stage 1, 2, and 3 build using this final patch.

Got any ideas on how to make this work on CHOST=i[3456]86-* stuff?  I have no
problem adding this, but don't want to introduce any new bugs/problems with it.

Well, that only works if someone puts 'export CC=cc' in their envscript, and
even then some builds don't work with it. The method is already broken to begin
with.

The proper way to do this is to build a i586-pc-linux-gnu "cross-compiler" on a
i686-pc-linux-gnu box or just create symlinks in the proper place.

OK.  I (finally) have a clue and have looked at this.  It looks good except for
the cleanup.  We don't want to just remove everything.  Instead, we should be
restoring it to its previous state, so we can still have a distcc package if
this were a LiveCD.

Created an attachment (id=117356) [details]
patch

This updates the patch to put /usr/lib/distcc/bin/ back to the way it was
before we touch it, instead of just clearing it all together.

OK.  This is in SVN now and will show up in 2.0.5_pre4 or later.

This should be fixed in 2.0.5_pre4.  Please test this version of catalyst (or
newer) and report back if it does not work.

Thanks