Summary: | gcc-config 1.3.8-r3 breaks distcc compiles on different architectures | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Gerald Britton <gerald.britton> |
Component: | [OLD] Development | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | amne |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Gerald Britton
2005-01-05 10:01:17 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" amne wants to add a comment, so reopened. 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. 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...) |