I've spent quite a bit of time figuring out this problem, so I'd just put this out there, hoping people can be warned when they see their build environment with distcc is suddenly borked after upgrading to Debian bullseye. I suspect that this problem is happenning in other distro, too.
Background:
I usually build kernels and u-boots natively in ARM boxes. And to improve the build time, I have a build farm of several ARM boxes, one is a distcc client and the rest are distcc servers. The client node builds the kernel, and parcels out gcc compiling jobs to other distcc nodes. This speeds up the build many times over. While I can build kernels with cross compiler on Debian-Ubuntu based system on powerful laptops, native compiling is always my preferred approach.
Problem:
Upgrade to Debian bullseye has broken this process for me. So to keep it going, I had to move my kernel/u-boot build environment to Linux Mint. Fantastic build time with a quad-core Intel i5 laptop.
Conclusion:
But I detemined to find out why it was broken, and discovered that just by removing distcc from the build process would fix it :) There seems to be some problems with GNU make in recognizing the soft links that point to where the gcc compiler suite is. distcc needs to masquerade the compiler location to point to where its own binaries are, and then actually calls the real compiler binaries to execute the jobs. So I suspect the fault is with GNU make, but not sure yet if any changes in GNU make to bullseye has caused this problem, or it is the distcc setup that needs to be modified.
-bodhi
===========================
Forum Wiki
bodhi's corner
Edited 2 time(s). Last edit at 01/01/2022 09:47PM by bodhi.