Bug 76788 – gcc-config 1.3.8-r3 breaks distcc compiles on different architectures

• Status: RESOLVED WONTFIX
• Product: Gentoo Linux

[Description Gerald Britton 2005-01-05 10:01:17 UTC]

I run two boxes: a Celeron running gentoo linux natively (i686) and a P4 running gentoo under colinux under Windows 2000 (i586). Before the latest gcc-config update (1.3.8-r3) the compiles all worked, since then they fail with messages like:

checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... configure: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details.

[config.log]

configure:2449: i686-pc-linux-gnu-gcc -o conftest -O2 -march=i686 -fomit-frame-pointer   conftest.c  >&5
configure:2452: $? = 0
configure:2477: result:
configure:2483: checking for suffix of object files
configure:2504: i686-pc-linux-gnu-gcc -c -O2 -march=i686 -fomit-frame-pointer  conftest.c >&5
distcc[22986] ERROR: compile /root/.ccache/conftest.tmp.ws-5130.att-intra.com.22982.i on 10.18.64.218 failed
Could not run/locate "i686-pc-linux-gnu-gcc"
configure:2507: $? = 1
configure: failed program was:
| /* confdefs.h.  */


It is trying to execute i686-pc-linux-gnu-gcc on my colinux box, which doesn't run, instead of gcc, which does.  I reverted to gcc-config 1.3.6 and all is working once again

Reproducible: Always
Steps to Reproduce:
1. emerge -u gcc-config (to latest level)
2. emerge -u xchat (for example)
3.
Actual Results:  
compile fails

Expected Results:  
compile succeeds

Gentoo Base System version 1.4.16
Portage 2.0.51-r3 (default-linux/x86/2004.0, gcc-3.3.4, glibc-2.3.4.20040808-r1,
2.6.9-gentoo-r9 i686)
=================================================================
System uname: 2.6.9-gentoo-r9 i686 Celeron (Mendocino)
distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled]
ccache version 2.3 [enabled]
Autoconf: sys-devel/autoconf-2.59-r5
Automake: sys-devel/automake-1.8.5-r1
Binutils: sys-devel/binutils-2.15.90.0.1.1-r3
Headers:  sys-kernel/linux-headers-2.4.21-r1
Libtools: sys-devel/libtool-1.5.2-r7
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O2 -march=i686 -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
COMPILER=""
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3.2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config
/usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/share/config /var/qmail/alias
/var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=i686 -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distcc distlocks sandbox sfperms"
GENTOO_MIRRORS="http://gentoo.osuosl.org
http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j5"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.ca.gentoo.org/gentoo-portage"
USE="x86 X acl acpi alsa arts avi berkdb bitmap-fonts crypt cups directfb encode
esd fam foomaticdb fortran gdbm gif gpm gtk gtk2 imagemagick imlib ipv6 java
jpeg krb4 libwww mad mikmod motif mpeg ncurses nls oggvorbis opengl pam pdflib
perl png python qt quicktime readline samba sdl slang spell ssl svga tcltk tcpd
tiff truetype xml2 xmms xv zlib"

[Comment 1 SpanKY 2005-01-05 14:58:02 UTC]

gcc-config isnt at fault really

it's because on the host machine, gcc is now being run as "i686-pc-linux-gnu-gcc" instead of as "gcc"

[Comment 2 Lars Weiler (RETIRED) 2005-01-08 11:11:33 UTC]

amne wants to add a comment, so reopened.

[Comment 3 Wernfried Haas (RETIRED) 2005-01-08 11:15:01 UTC]

I have the same problem here with 2 boxes, one i586 and one i686. After upgrading gcc-config to 1.3.8-r3 (-r4 on the other box) distcc didn't work any more. I noted that $CC isn't set to gcc any more and debug in distcc showed that i686-pc-linux-gnu-gcc was executed on the i586 box - which resulted in failure.
If it's not gcc-config's fault, the fault is somewhere else in Gentoo (e.g. distcc, gcc, choose someone to blame ;-) ). If it's not Gentoo's fault but mine, i'd highly appreciate any hints how to solve it.

PS: Thanks Lars.

[Comment 4 Jeremy Huddleston (RETIRED) 2005-01-08 13:38:10 UTC]

This isn't a problem with gcc-config.  It's a problem with your fistcc layout.   You don't have i686-pc-linux-gnu-gcc installed on the other system.  Chances are you can just symlink i686-pc-linux-gnu-gcc to gcc on that system, and you'll be fine (don't forget to do it for g++, g77, etc...)