When I attempt to update to sablotron 1.0.1, the configure script dies with the following error: checking for style of include used by make... GNU checking for i686-pc-linux-gnu-gcc... gcc checking for C compiler default output... configure: error: C compiler cannot create executables See `config.log' for more details. !!! ERROR: app-text/sablotron-1.0.1 failed. !!! Function econf, Line 365, Exitcode 77 !!! econf failed config.log is quite large, however, I will attach to this bug. All other applications build fine and no other builds give me problems. Reproducible: Always Steps to Reproduce: 1. emerge sablotron 1.0 2. attempt an update to 1.0.1 3. Portage 2.0.50-r1 (default-x86-1.4, gcc-3.3.3, glibc-2.3.3_pre20040207-r0, 2.4.25) ================================================================= System uname: 2.4.25 i686 Intel(R) Pentium(R) 4 CPU 2.00GHz Gentoo Base System version 1.4.3.13p1 distcc 2.13 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.59-r3 Automake: sys-devel/automake-1.8.2 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=pentium3 -O3 -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=pentium3 -O3 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://192.168.10.198/ http://gentoo.mirrors.pair.com/ ftp://gentoo.mirrors.pair.com/ http://mirrors.tds.net/gentoo http://open-systems.ufl.edu/mirrors/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://192.168.10.198/gentoo-portage" USE="X509 acl apache2 berkdb chroot clamav crypt curl flexresp freetype gd gdbm geoip gif imagemagick imap imlib2 innodb jpeg kde libg++ libwww mbox mcal minimal mmx mysql nagios-dns nagios-ntp nagios-ping nagios-ssh ncurses nls oav oci8 odbc offensive oggvorbis pam pdflib perl php pic png prelude python readline samba snmp spell sse ssl tcpd tiff truetype wmf x86 xfs xml xml2 zlib"
Created attachment 26842 [details] Sablot 1.0.1 config.log
the reason that gcc can not make executables is that it has problems with -lstdc++ which is a flag that the configure script enables. here is what happens when i try to enable this flag: $ gcc -lstdc++ /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/../../../crt1.o(.text+0x18): In function `_start': : undefined reference to `main' /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/libstdc++.so: undefined reference to `_Unwind_Resume_or_Rethrow@GCC_3.3' collect2: ld returned 1 exit status I know i have no file arguements, but if that was an issue it would say: gcc: no input files
This fails for me as well
Please check your /etc/ld.so.conf if there are any entries which shouldn#t be there.I had two entries in there. /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3 /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2 If you got two entries please check if in the directory /etc/env.d/gcc/ there are two files, one called i686-pc-linux-gnu-3.3.2 and the other i686-pc-linux-gnu-3.2.3. If so, remove i686-pc-linux-gnu-3.2.3 and then run env-update source /etc/profile gcc-config i686-pc-linux-gnu-3.3.2 This did the trick on my system
I still get the same error on mine, closer inspection reveals two gcc lines in /etc/ld.so.conf after doing the env-update et al - one for gcc-3.2.2 and one for gcc-3.2.3 This occurs even if 3.2.3 is the only one I leave in there before the env-update And it still dies
woops I'm an idiot and can't read - this fix worked.
OK, if you run into more problems, you should check if any libraries in the directory /usr/lib are still linked to the old gcc-libraries. for i in /usr/lib/*; do [ -f $ i ] && ldd $i | grep [GCC-VERSION]; done in your case for i in /usr/lib/*; do [ -f $ i ] && ldd $i | grep 3.2.2; done In my case libaspell and libpspell were linked to the old libraries, so I had to reemerge aspell: emerge aspell Can someone change the state of this BUG to FIXED?
done
*** Bug 99687 has been marked as a duplicate of this bug. ***