On Tue, 28 Oct 2025, Greg Troxel wrote:
We're having a similar problem with go, that I mentioned long ago, and seems not fixed. I tried to fix it, but go seems super insistent on spinning up n threads equal to ncpu. Combined with a reasonable MAKE_JOBS, that's really problematic besides being wrong.
Sorry for that. It's on my backlog. -- Benny