On Mon, Dec 2, 2019 at 1:23 PM Erik Rull via distcc <[email protected]> wrote:
> Hi all, > > I used distcc some years ago already. Then computing power grew and I > wasn't in the need of using it. > Meanwhile I have multiple gcc versions and processor type targets (with > different compiler versions) that make the compilation lasting long again. > In earlier days I asserted that all distcc slaves were equipped with a > single gcc and they had the same version as the host. > Regarding each architecture, I can guarantee that. But each processor > architecture as a different GCC running, so there is no "common" gcc call > for all target systems because they are located in different build > environments on the machines. > How can I parameterize distcc so that this can be resolved? I would need > e.g. for each gcc compilation a different path that each slave would know. > > I didn't find an easy solution for that or I didn't see find the right > sections in the manual :-) > > I know where each compiler is for each architecture on each slave, I just > need to know how to connect them properly with distcc... > Does this mean that you have multiple version of gcc installed something like this? /usr/local/gcc-7, /usr/local/gcc-6 etc? Or that you call gcc by full name like this: x86_64-linux-gnu-gcc-6.4.0 x86_64-linux-gnu-gcc-7.1? If the latter: export CC="distcc x86_64-linux-gnu-gcc-4.5"
__ distcc mailing list http://distcc.samba.org/ To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/distcc
