This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: distributed compilation with gcc: distcc

From: Martin Pool <mbp at samba dot org>
To: Aldy Hernandez <aldyh at redhat dot com>
Cc: gcc at gcc dot gnu dot org, distcc at lists dot samba dot org
Date: Tue, 23 Jul 2002 10:30:30 +1000
Subject: Re: distributed compilation with gcc: distcc
References: <20020722085822.GG6023@samba.org> <m3fzybqz7j.fsf@flamingo.sfbay.redhat.com>

[cc'd distcc list]

I just looked at  

  http://subversions.gnu.org/cgi-bin/viewcvs/gcc/gcc/gcc/Makefile.in?rev=1.912&content-type=text/vnd.viewcvs-markup

which makes things a bit clearer than the parent Makefile.  

So it seems like we have to at least have the $(build_tooldir), and
the $(builddir)/stage[1234] directories shared or copied across all
the machines.  In addition, for the special case of gcc which runs its
own output, all the volunteers will need to be compatible
architectures and OSs.

I suspect the easiest thing will be to share the builddir over NFS.
Is that possible?

-- 
Martin

Follow-Ups:
- Re: distributed compilation with gcc: distcc
  - From: Alexandre Oliva
- Re: distributed compilation with gcc: distcc
  - From: Ben Elliston

References:
- distributed compilation with gcc: distcc
  - From: Martin Pool
- Re: distributed compilation with gcc: distcc
  - From: Aldy Hernandez

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]