I just re-installed my system as I do a couple of times a year (format and starting over again) using 2004.2 and everything went as expected except now when I try to install KDE updates I get this failure: checking if C++ programs can be compiled... no configure: error: Your Installation isn't able to compile simple C++ programs. Check config.log for details - if you're using a Linux distribution you might miss a package named similiar to libstd++-dev. !!! ERROR: kde-base/kdegraphics-3.3.1-r2 failed. !!! Function kde_src_compile, Line 130, Exitcode 1 !!! died running ./configure, kde_src_compile:configure !!! If you need support, post the topmost build error, NOT this status message. The system has kde 3.3.1 on it that I compiled from scratch after I got a stage 3 system yet I get this now. I always build my systems from stage 1. Here's emerge info: ws1 ~ # emerge info Portage 2.0.51-r3 (default-x86-2004.2, gcc-3.3.4, glibc-2.3.4.20041102-r0, 2.6.10-rc1 i686) ================================================================= System uname: 2.6.10-rc1 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz Gentoo Base System version 1.6.5 distcc 2.18 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] 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.92.0.2-r1 Headers: sys-kernel/linux26-headers-2.6.8.1-r1 Libtools: sys-devel/libtool-1.5.2-r6 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=pentium4 -fomit-frame-pointer -funroll-loops -pipe" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/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/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=pentium4 -fomit-frame-pointer -funroll-loops -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distlocks fixpackages" GENTOO_MIRRORS="http://gentoo.osuosl.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j19" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X alsa apm arts avi berkdb bitmap-fonts cdr crypt cups dvd dvdr encode f77 foomaticdb gdbm gif gphoto2 gpm gstreamer gtk gtk2 imlib java jpeg kde ldap libg++ libwww mad mikmod mime motif mp3 mpeg ncurses nls nowin nptl objc oggvorbis opengl oss pam pda pdflib perl pic png ppds python qt quicktime quotes readline samba scanner sdl slang spell sse ssl svg svga tcltk tcpd threads tiff truetype usb wmf x86 xml2 xmms xv zlib" 2004.0 and .1 did not do this to me and I follow the exact same procedure when I reinstall my systems. As an FYI I've installed gentoo hundreds of times before going back to the early 1.x days (just so you know my background). It's always possible I made a mistake but I find it odd that I completely rebuilt this system and compiled KDE and a lot of apps then this happens. I'm not exactly sure what the problem is. C++ is in the /usr/bin directory and in the path. Let me know and I sill supply anything else you need. Thanks!
This isn't related to kde, but is a problem with your build system. please attach the file config.log under /var/tmp/portage/kdegraphics-3.3.1-r2/work/kdegraphics-3.3.1/
Created attachment 43724 [details] /var/tmp/portage/kdegraphics-3.3.1-r2/work/kdegraphics-3.3.1/config.log What's odd is the entire system was built with the same make.conf from stage 2 on. Per the directions I don't touch the make.conf until after stage 1. I'm hoping to avoid rebuilding the system again so soon especially when I have no idea why this suddenly happened and another day to reinstall only to have it happen again would really suck. :)
you try should running gcc-config -l and then gcc-config NUM where NUM is the numbero on the left of one listed gcc compiler you want to use. let us know if this works.
Any news on this?
The gcc-config thing worked. Someone might want to look into how that is changed with updates. Doing a normal well practiced install with the new 2004.3 got me into this. My normal process is to wait until after bootstrapping to change anything in the make.conf When it is time to do a emerge system I copy over my backed up make.conf from the previous install and then do the emerge system. It's always worked well until 2004.3 If that's bad practice I have no problems changing my process.
toolchain: any though on this? it this a gcc ebuilds problem that will not call gcc-config correctly?
should be resolved already by other bugs
