[distcc] local builds fails with -fPIC ?

[Dag Wieers]

On Sun, 1 Feb 2004, Martin Pool wrote:

> On  1 Feb 2004, Dag Wieers <dag at wieers.com> wrote:
> > I'm having a strange problem. When no distcc-server is available and 
> > distcc decides to run a task locally, it fails.
> > 
> > 	configure:5648: checking for i386-redhat-linux-gcc-3.3.2 option to produce PIC
> > 	configure:5825: result: -fPIC
> > 	configure:5833: checking if i386-redhat-linux-gcc-3.3.2 PIC flag -fPIC works
> > 	configure:5854: i386-redhat-linux-gcc-3.3.2 -c -O2 -march=i386 -mcpu=i686  -fPIC -DPIC conftest.c >&5
> > 	distcc[32203] (dcc_build_somewhere) Warning: failed to distribute, running locally instead
> > 	configure:5858: $? = 0
> > 	configure:5866: result: no
> > 
> > For some reason configure thinks -fPIC is not supported although it works 
> > if a distcc-server is started. This causes some software to not work when 
> > build with distcc (but without distcc-servers). If build without distcc, 
> > it works (as -fPIC is supported).
> 
> I think this is because configure interprets the occurrence of any
> stderr messages as meaning "failed".  Sucks.  

That explains it.


> All I can suggent for the moment is not to have down hosts in the list
> when running configure, or set DISTCC_LOG.

Well, that's not an option currently (unless there's an automatic way to 
discover it like on MacOSX). My setup has to be flexible wrt that.

When I use DISTCC_LOG, I get much more output than I would like, stuff 
like:

	checking errno.h presence... distcc[1897] exec on localhost: i386-redhat-linux-gcc-2.96 -E -I. conftest.c
	distcc[1897] (dcc_collect_child) cc times: user 0.010000s, system 0.000000s, 53 minflt, 245 majflt
	distcc[1897] compile on localhost completed ok
	distcc[1897] elapsed compilation time 0.007820s
	distcc[1897] (dcc_exit) exit: code 0; self: 0.000000 user 0.000000 sys; children: 0.010000 user 0.000000 sysyes

Where it used to be only one line. Even when I define DISTCC_VERBOSE=0 I 
get this much output. Is there no way to reduce (or suspend) all output 
from distcc. To prevent it from contaminating my build environment.

Whenever I get in trouble I can still enable all debugging output and 
redirect to a logfile.

Kind regards,
--   dag wieers,  dag at wieers.com,  http://dag.wieers.com/   --
[Any errors in spelling, tact or fact are transmission errors]