On 1 Feb 2004, Dag Wieers <[EMAIL PROTECTED]> wrote: > Hi, > > 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. All I can suggent for the moment is not to have down hosts in the list when running configure, or set DISTCC_LOG. -- Martin
pgp00000.pgp
Description: PGP signature
__ distcc mailing list http://distcc.samba.org/ To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/distcc
