[distcc] distcc, cross-compilers & packages that ignore CC/CXX... what's the _right_ way?

[Lisa Seelye]

On Mon, 2006-01-23 at 21:19 -0600, Andrew Gaffney wrote:
> Dan Kegel wrote:
> > On 1/23/06, Stuart Longland <redhatter at gentoo.org> wrote:
> > 
> >>We were just having a discussion (read: heated debate) regarding how to
> >>set up distcc to work with cross-compiling toolchains.  The fly in the
> >>ointment is dealing with certain packages, which ignore the CC and CXX,
> >>and just call `gcc` (or worse, `cc`) instead of the fully qualified
> >>compiler name (`mips-unknown-linux-gnu-gcc`...etc).
> >>
> >>        There are a couple of approaches that we've nutted out:
> >>
> >>1. Multiple distcc daemons on separate ports: ...
> >>2. Single distcc daemon, with client-side wrappers. ...
> >>
> >>So... I put the question to you, the developers... what's the correct
> >>way to handle these "special" cases?  Is there a better way of handling
> >>this?
> > 
> > Yes.  Fix the broken packages and send the fixes upstream.
> > That's what I do.
> 
> And for dead, slow, incompetent, or otherwise uncooperative upstreams? I don't 
> think that's what he had in mind.

For Gentoo a solution might be RESTIRCT="crosscompile". Dan is right,
though, make the corrective patches public and hope they're implemented
upstream eventually.

-- 
Regards,
Lisa Seelye
GPG: 09CF5 2D6B8 2B72B 997A7 601BC B46B5 561E4 96FC5
http://www.thedoh.com/~lisa/site
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.samba.org/archive/distcc/attachments/20060124/4e96ab04/attachment.bin