Thankyou for the report. On 12 Aug 2003, Kirtis Bakalarczyk <[EMAIL PROTECTED]> wrote:
> During an emerge -u world libxml2 failed on me with the following errors: > > gcc -DHAVE_CONFIG_H -I. -I. -I. -I./include -I./include -D_REENTRANT -O2 -march= > pentium4 -mmmx -msse2 > -pipe -Wall -c nanoftp.c -fPIC -DPIC > distcc[15832] (dcc_build_somewhere) Warning: failed to distribute, running local > ly instead > nanohttp.c: In function `xmlNanoHTTPConnectAttempt': > nanohttp.c:913: `len' undeclared (first use in this function) > nanohttp.c:913: (Each undeclared identifier is reported only once > nanohttp.c:913: for each function it appears in.) > distcc[15832] ERROR: compile on localhost failed with exit code 1 > make[2]: *** [nanohttp.lo] Error 1 > make[2]: *** Waiting for unfinished jobs.... This very much looks like a real failure in libxml, not anything to do with distcc, particular because the fallback mechanism made it not be built locally. In fact, I seem to recall seeing that exact failure with libxml. I think there is some problem with its dependencies or autoconf script. Perhaps it's not finding the right type for some kind of *len_t typedef? Can you have a look at that location in the source and work out what's going wrong? > !!! ERROR: dev-libs/libxml2-2.5.9 failed. > !!! Function src_compile, Line 37, Exitcode 2 > !!! (no error message) > > It's not unexpected that it would fail to distribute the build, > since I haven't gotten around to installing distcc on my other > computers. The reason i'm reporting this here and not to the > libxml2 people is that libxml2 builds fine when I remove distcc from > gentoo's FEATURES in make.conf (disabling it). Are you 100% sure you didn't change anything else in between builds, like installing another package? > distcc[9890] (dcc_spawn_child) forking to execute: gcc -DHAVE_CONFIG_H -I. -I. -I. > -I./include -I./include -D_REENTRANT -O2 -march=pentium4 -mmmx -msse2 -pipe -Wall -c > -fPIC -DPIC -o /root/.ccache/tmp.hash.3jane.9886.o > /root/.ccache/tmp.stdout.3jane.9886.i > distcc[9891] (dcc_increment_safeguard) setting safeguard: _DISTCC_SAFEGUARD=1 > distcc[9890] (dcc_spawn_child) child started as pid9891 > distcc[9890] (dcc_collect_child) cc child 9891 terminated with status 0x100 > distcc[9890] (dcc_collect_child) cc times: user 0.459930s, system 0.038994s, 1820 > minflt, 1163 majflt > distcc[9890] ERROR: compile on localhost failed with exit code 1 > distcc[9890] elapsed compilation time 0.527710s > distcc[9890] (dcc_exit) exit: code 1; self: 0.002999 user 0.002999 sys; children: > 0.459930 user 0.038994 sys > distcc[9890] (dcc_cleanup_tempfiles) deleted 0 temporary files This is normal for a local build. Would you please set DISTCC_SAVE_TEMPS=1 and post the preprocessed input (.i file)? -- Martin __ distcc mailing list http://distcc.samba.org/ To unsubscribe or change options: http://lists.samba.org/cgi-bin/mailman/listinfo/distcc
