gdb's configure calls short compiler name what breaks its distributed build. Not once I have spotted during emerge' ./configure run output of x86 gcc complaining about unrecognized - powerpc specific - options. Reproducible: Always Steps to Reproduce: 1. main host on powerpc 2. compile farm on x86 with crossdev -t powerpc 3. configure distcc/distccd 4. on powerpc do "emerge gdb" Actual Results: 1. In configure output watch for x86 gcc complaining about unsupported options. 2. configure fails without error message (I presume something compiled during configure run - and compiled remotely with foreign gcc - fails to run on host due to different arch.) Expected Results: No compiler errors should be reported and configure should succeed w/o problems as in non-distributed build. Build should go on.
Watching now non-distributed build process, it seems that GDB does ignore configure's "--host" parameter entirely: it always calls "gcc" instead of fully qualified compiler name.
What version was this with? When compiling the newest ~arch gdb it seems to use the full compiler name: x86_64-pc-linux-gnu-gcc -c -DHAVE_CONFIG_H -I. -I.././readline -DRL_LIBRARY_VERSION='"5.1"' -march=nocona -O2 -pipe terminal.c Please reopen if you are still having problems.
