"James Ausmus" <[EMAIL PROTECTED]> writes: [...]
> OK, what does the output of gcc-config -l (ell) show you - what > version of gcc is currently being used? Did gcc get updated prior to > the glibc update attempt? If so, was env-update && source /etc/profile > run after the gcc update? It outputs the list of possible profiles and I think the asterisk shows what I'm running. And also verified that by gcc --version: [1] i686-pc-linux-gnu-3.3.6 * [2] i686-pc-linux-gnu-3.3.6-hardened [3] i686-pc-linux-gnu-3.3.6-hardenednopie [4] i686-pc-linux-gnu-3.3.6-hardenednopiessp [5] i686-pc-linux-gnu-3.3.6-hardenednossp [6] i686-pc-linux-gnu-3.4.6 [7] i686-pc-linux-gnu-3.4.6-hardened [8] i686-pc-linux-gnu-3.4.6-hardenednopie [9] i686-pc-linux-gnu-3.4.6-hardenednopiessp [10] i686-pc-linux-gnu-3.4.6-hardenednossp I believe gcc was updated prior to glibc and no I didn't run the env-update && source /etc/profile However I have done so now and get what appears to be the same failure on glibc. I've looked through the INSTALL file for glibc and it does specify a newer version of gcc than I am running. Recommended Tools for Compilation ================================= [...] * GCC 3.4 or newer, GCC 4.1 recommended So it appears then that something is wrong with this update process. emerge -v -uDp gcc doesn't want to update the current gcc which is 3.3.6 yet the glibc it wants to install requires a newer gcc.... bad. In fact running emerge -v -uDp gcc only wants to (U) update glibc to a version that requires a newer gcc to be installed. Something is very wrong in this picture. I'm tempted to try installing a newer gcc like maybe gcc-4* and see if that cures this problem.... do you think that would be wise? -- gentoo-user@gentoo.org mailing list