On 5 Nov 2003, "Ahlborn, James T (MED)" <[EMAIL PROTECTED]> wrote: > Hi, > It took me a long time to figure out how to get icc (7.0) to work with > distcc (2.11.2), and it turned out to be a rather silly problem. I > would get errors on some remote clients that looked like: > > icc: error: unable to open 'iccSDFAgas' > > The actual problem is that icc likes to create some random little temp > files in the directory in which the build is running (and although icc > *claims* that it uses the TMP environment variable, it seemed to ignore > it for these temp files). since the daemon is currently run in '/', icc > is unable to create these temp files (depending on the permission of > that dir on different boxes). it seems to me that this problem can be > fixed in one of two ways (well, intel could fix their compiler...):
I think you should file a bug with Intel. > 1. come up with various scripts that redirect to the actual intel > compiler, and along the way change the current dir if we are in the '/' > dir. this seems like too much work, for what seems to me to be a simple > problem. > > 2. add on option to distccd for which dir to run the compiler in (or > just use the TMPDIR). This would fix your problem. I don't know if it is very generally desirable; it's a good standard behaviour for daemons to run from /. Rather than adding an option you should probably just snip out the chdir(/) line. -- Martin
pgp00000.pgp
Description: PGP signature
__ distcc mailing list http://distcc.samba.org/ To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/distcc
