Summary: | gcc-3.4.4 failed to compile | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Carl A. Dunham <gentoo-bugs2> |
Component: | [OLD] Development | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | herber |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Other | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Carl A. Dunham
2005-06-06 06:27:32 UTC
i aswell cant compile gcc 3.4.4 on my amd64 i think it dies in multilib pass checking for x86_64-pc-linux-gnu-gcc... /var/tmp/portage/gcc-3.4.4/work/build/gcc/xgcc -B/var/tmp/portage/gcc-3.4.4/work/build/gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include -m32 checking for C compiler default output file name... a.out checking whether the C compiler works... configure: error: cannot run C compiled programs. If you meant to cross compile, use `--host'. See `config.log' for more details. make[1]: *** [configure-target-libstdc++-v3] Error 1 make[1]: Leaving directory `/var/tmp/portage/gcc-3.4.4/work/build' make: *** [profiledbootstrap] Error 2 !!! ERROR: sys-devel/gcc-3.4.4 failed. !!! Function gcc_do_make, Line 1205, Exitcode 2 !!! emake failed with profiledbootstrap !!! If you need support, post the topmost build error, NOT this status message. *** Bug 95640 has been marked as a duplicate of this bug. *** Same here. This profile 2004.3 is the latest profile for SELinux, are there any maintainers encoutering this bug? A workaround would be most welcome. Not being able to compile gcc is pretty scary. I have solved this problem on my system. It seems that there are times when the toolchain gets misconfigured after what I consider a simple upgrade. After lots of forum and bugzilla checking I ran a combination of these commands, along with the same commands to 'fix' whatever was wrong, and now everything is working: gcc-config -l # to make sure I had the right compiler fix_libtool_files.sh # on every old gcc version I ever had binutils-config -l # to make sure I had the right tool chain source /etc/profile # in case anything had changed etc-update # to pick up any configuration changes Now I am wondering how many of the -config commands I need to run after a system update. These give interesting results: find /sbin /bin /usr/sbin /usr/bin -print|grep config find /sbin /bin /usr/sbin /usr/bin -print|grep config|wc -l I have 108 -config commands on my system. I wish this bug report would help generate a master fix_config script. Thanks! Steve: most of those -config packages are like gtk-config (they are used to get CFLAGS and LDFLAGS for building packages with that library). They're mostly not like gcc-config. Those config binaries are tending to find there way into pkg-config and the old ones getting deprecated as time goes on... As for the amd64 multilib bug, that's a differnet bug... please open a new one one with appropriage emerge --info |