On 13 Dec 2002, David Sanderson <[EMAIL PROTECTED]> wrote: > I'm trying to figure out how we could use distcc for our compilation > needs, and I've run into a problem. Our compilation system uses the > environment (particularly, PATH) to choose between compilers, rather > than the compiler's name or its command-line switches. A single build > might use several compilers selected in this way. > > We already have an infrastructure set up that makes a given compiler > available under the same directory on all our machines, so if distccd > could run its command using the environment inherited by the distcc > command, it could then automatically run the correct compiler on > distcc's behalf.
I'm not sure it's really necessary to add that to distcc itself. You can pass a fully-qualified compiler name to distcc, e.g. distcc /opt/gcc-2.32939213/bin/gcc -c hello.c and it will pass that across the network and use it on the server. -- Martin _______________________________________________ distcc mailing list [EMAIL PROTECTED] http://lists.samba.org/cgi-bin/mailman/listinfo/distcc
