[distcc] Problem using TMPDIR with Cygwin version of distcc

Harig, Mark maharig at idirect.net
Sat Dec 13 20:03:13 GMT 2003


 
> > 1. I have been unable to change the location where 
> temporary files were written, as reported in 
> /var/log/distccd.log.  I tried both exporting the TMPDIR 
> environment variable and including it on the command-line for 
> 'make', that is:
> > 
> >     $ export TMPDIR=[somedir]
> >     $ make -j4 CC="distcc ..."
> > 
> >    and 
> > 
> >     $ make -j4 TMPDIR=[somedir] CC="distcc ..." 
> > 
> >    Because I was not able to redirect the location that 
> distcc writes the temporary files, I worked around this 
> problem by creating a mount point (on each of the distccd 
> servers) where distcc expects the files to be written:
> > 
> >     $ mount c:/tmp /tmp
> 
> This will control where the client writes its temporary files, barring
> some unknown bug.  But setting TMPDIR for the client obviously won't
> affect the server process.  You need to set TMPDIR when you run the
> server.
> 

I was not able to find any mention of TMPDIR in the manual 
page for the server, 'distccd', although it is described in
the manual page for the client, 'distcc'.  Is this included
in a later version?  I am using distcc 2.11.2-1.

> > 2. Also, is there any way to retain the temporary files that
> > 'distcc' creates, i.e., /tmp/*.i, /tmp/*.o, etc.?  I would like to
> > be able sometimes to inspect these files in case they provide clues
> > about problems.
> 
> rtfm:
> 
>      DISTCC_SAVE_TEMPS
>         If set to 1, temporary files are not deleted  after  
> use.   Good  for
>         debugging, or if your disks are too empty.
> 

Oops!  I missed that.  Sorry.  Thanks.

-----



More information about the distcc mailing list