This is the mail archive of the
mailing list for the GCC project.
Re: distributed compilation with gcc: distcc
- From: Martin Pool <mbp at samba dot org>
- To: gcc at gcc dot gnu dot org
- Cc: distcc at lists dot samba dot org
- Date: Thu, 1 Aug 2002 22:26:03 +1000
- Subject: Re: distributed compilation with gcc: distcc
- References: <20020722085822.GG6023@samba.org> <firstname.lastname@example.org> <1027370776.20668.14.camel@frodo> <20020722140125.A11071@redhat.com> <20020722234237.GG5692@samba.org> <20020722170531.C11613@redhat.com>
On 22 Jul 2002, Aldy Hernandez <email@example.com> wrote:
> > The biggest dependency on the clients is that they must have a version
> > of gcc that is "sufficiently reasonable" to compile the preprocessed
> hmm, this is fine [most of the time] for building gcc because this
> only affects the first stage build. but that's the point of my other
> post-- we'd all probably be delighted to use this, if it could handle
> parallelizing the other stages.
> in which case, you're going to have to design a mechanism to use the
> recently built compiler to rebuild itself, target libraries, and
> other languages (c++, java, etc). (see my previous email)
Java's model for this kind of thing is obvious very different from C.
I think you could probably do something broadly similar to distcc, but
the details would be quite different, and it perhaps should be a
separate program. I don't use Java much these days so I probably will
not do it any time soon.