Thomas Deutschmann wrote:
> 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.
OK.
The thing to look at, I would say, is
- the command-line arguments that distcc passes to gcc for each compilation,
- the contents of conftest2.o (it appears to be a copy of conftest1.o although
it shouldn't).
> > > > 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 ;-)
Good. They learned it the hard way:
https://github.com/distcc/distcc/commit/dfd079fe3e09745c70647afeb8e90f1b82aaad37
;-)
Bruno
