Hi, Bruno Haible wrote: > Looks like distcc, or the distcc installation and configuration on the > particular user's machine (*), is broken. I won't investigate that. > > [...] > > (*) AFAIK, the same version of the same program frequently behaves > differently on different Gentoo machines. Please correct me if I'm wrong.
You are wrong: If you use exact same configuration you will get exact same results (it is the same like doing reproducible builds RedHat, Ubuntu, Debian...). Of course, if you are changing something, you will get different results. And given that most Gentoo users have compiled their own toolchain any early difference will spread across the whole system. But in this case I am very confident that this isn't a problem on a particular user's machine, given that multiple user have reported the same problem. The issue is spreading across packages given that more and more new releases will contain an updated gnulib which contains the 'bad commit' causing the problem. I was able to reproduce this with latest distcc-3.3.2 version. So if this is caused by distcc, it is still a problem. I'll try to reproduce the problem using two Debian Stretch hosts. > > > distcc[20786] ERROR: compile (null) on localhost failed > > While at it, you can also investigate why distcc passes a NULL string > to fprintf. (It surely does not pass the string "(null)"?) This is not > valid in POSIX. It is really passing the string "(null)", see https://github.com/distcc/distcc/blob/master/src/exec.c#L574 ;-) -- Regards, Thomas Deutschmann / Gentoo Linux Developer C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5
signature.asc
Description: OpenPGP digital signature
