Using sys-devel/distcc-2.17-r1. distcc only uses localhost as shown by: $ distcc-config --get-hosts localhost With distcc in FEATURES line, emerging gettext fails: creating msgcat /bin/sh ../libtool --mode=link gcc -march=pentium4 -O3 -pipe -s -fomit-frame-pointer -fforce-addr -falign-functions=4 -fprefetch-loop-arrays -ffast-math -o msgen msgen-msgen.o libgettextsrc.la gcc -march=pentium4 -O3 -pipe -s -fomit-frame-pointer -fforce-addr -falign-functions=4 -fprefetch-loop-arrays -ffast-math -o .libs/msgcomm msgcomm-msgcomm.o ./.libs/libgettextsrc.so /var/tmp/portage/gettext-0.12.1-r2/work/gettext-0.12.1/gettext-tools/lib/.libs/libgettextlib.so -lc msgmerge-msgmerge.o(.text+0x1ede): In function `message_merge': : undefined reference to `__builtin_stpcpy' msgmerge-msgmerge.o(.text+0x1ef5): In function `message_merge': : undefined reference to `__builtin_stpcpy' msgmerge-msgmerge.o(.text+0x1f24): In function `message_merge': : undefined reference to `__builtin_stpcpy' msgmerge-msgmerge.o(.text+0x1f53): In function `message_merge': : undefined reference to `__builtin_stpcpy' msgmerge-msgmerge.o(.text+0x1f82): In function `message_merge': : undefined reference to `__builtin_stpcpy' msgmerge-msgmerge.o(.text+0x1fb1): more undefined references to `__builtin_stpcpy' follow collect2: ld returned 1 exit status distcc[31017] ERROR: compile (null) on localhost failed make[4]: *** [msgmerge] Error 1 make[4]: *** Waiting for unfinished jobs.... gcc -march=pentium4 -O3 -pipe -s -fomit-frame-pointer -fforce-addr -falign-functions=4 -fprefetch-loop-arrays -ffast-math -o .libs/msgconv msgconv-msgconv.o ./.libs/libgettextsrc.so /var/tmp/portage/gettext-0.12.1-r2/work/gettext-0.12.1/gettext-tools/lib/.libs/libgettextlib.so -lc gcc -march=pentium4 -O3 -pipe -s -fomit-frame-pointer -fforce-addr -falign-functions=4 -fprefetch-loop-arrays -ffast-math -o .libs/msgen msgen-msgen.o ./.libs/libgettextsrc.so /var/tmp/portage/gettext-0.12.1-r2/work/gettext-0.12.1/gettext-tools/lib/.libs/libgettextlib.so -lc creating msgattrib creating msgunfmt creating msgcomm creating msgfmt xgettext-xgettext.o(.text+0x1a0f): In function `remember_a_message': : undefined reference to `__builtin_stpcpy' xgettext-xgettext.o(.text+0x1a1b): In function `remember_a_message': : undefined reference to `__builtin_stpcpy' xgettext-xgettext.o(.text+0x1a2d): In function `remember_a_message': : undefined reference to `__builtin_stpcpy' xgettext-xgettext.o(.text+0x1cea): In function `remember_a_message_plural': : undefined reference to `__builtin_stpcpy' xgettext-xgettext.o(.text+0x1cf6): In function `remember_a_message_plural': : undefined reference to `__builtin_stpcpy' xgettext-xgettext.o(.text+0x1d08): more undefined references to `__builtin_stpcpy' follow collect2: ld returned 1 exit status distcc[31283] ERROR: compile (null) on localhost failed make[4]: *** [xgettext] Error 1 make[3]: *** [all] Error 2 make[3]: Leaving directory `/var/tmp/portage/gettext-0.12.1-r2/work/gettext-0.12.1/gettext-tools/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/gettext-0.12.1-r2/work/gettext-0.12.1/gettext-tools' make[1]: *** [all] Error 2 make[1]: Leaving directory `/var/tmp/portage/gettext-0.12.1-r2/work/gettext-0.12.1/gettext-tools' make: *** [all-recursive] Error 1 !!! ERROR: sys-devel/gettext-0.12.1-r2 failed. !!! Function src_compile, Line 52, Exitcode 2 !!! (no error message) !!! If you need support, post the topmost build error, NOT this status message. On the other hand, running $ FEATURES="-distcc" emerge gettext results in a successful build. $ emerge -pv gettext These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] sys-devel/gettext-0.12.1-r2 -bootstrap -emacs +nls 0 kB
Created attachment 41388 [details] emerge --info
Try being a little less insane with your CFLAGS. Tone them back to -march=pentium4 -Os -pipe and try again. If you have only localhost in your hosts file then distcc will send the commands directly to gcc - there is no distcc action involved aside from being called via the symlink.
Let me see if I understand you correctly here. Basically you are saying that distcc will not allow me to use the "insane" CFLAGS (even if it is only compiling on localhost). However, on the other hand compiling with the same "insane" flags and without involving distcc let's me compile this (and other) packages fine. Sounds like a shortcoming of distcc?? Is distcc that sensitive to CFLAGS. I'm sure there is more to distcc than meets the eye, but from a 30,000 feet perspective it is supposed to be a wrapper around gcc.
I'm going to go ahead and close this bug as I think this is a local config issue.
