/usr/lib64/ocaml/Makefile.config:# generated by ./configure --prefix /usr --bindir /usr/bin --libdir /usr/lib64/ocaml --mandir /usr/share/man -target x86_64-pc-linux-gnu -host x86_64-pc-linux-gnu -cc x86_64-pc-linux-gnu-gcc-4.9.2 -as x86_64-pc-linux-gnu-as -aspp x86_64-pc-linux-gnu-gcc-4.9.2 -c -partialld x86_64-pc-linux-gnu-ld -r --with-pthread /usr/lib64/ocaml/Makefile.config:BYTECC=x86_64-pc-linux-gnu-gcc-4.9.2 /usr/lib64/ocaml/Makefile.config:NATIVECC=x86_64-pc-linux-gnu-gcc-4.9.2 /usr/lib64/ocaml/Makefile.config:ASPP=x86_64-pc-linux-gnu-gcc-4.9.2 -c /usr/lib64/ocaml/Makefile.config:MKDLL=x86_64-pc-linux-gnu-gcc-4.9.2 -shared -Wl,-O1 -Wl,--as-needed -Wl,--hash-style=gnu /usr/lib64/ocaml/Makefile.config:MKMAINDLL=x86_64-pc-linux-gnu-gcc-4.9.2 -shared -Wl,-O1 -Wl,--as-needed -Wl,--hash-style=gnu And now random packages fail to build trying to use this no-longer-existent gcc version.
Oh, it's also included in executables. Really awesome.
yes, it is known and documented by upstream: feel free to poke them about hardcoding it in Makefile.config and other places and if there's a way to make it dynamic, but I doubt this will be changed. On the other hand, you seem to have messed up $CC: it uses tc-getCC & friends, which here is x86_64-pc-linux-gnu-gcc and I've never seen it using versionned $CC...
No, I haven't 'messed it up'. I am using the only CC that makes sense in distcc environment.