Bug 137231 – emerging eselect-compiler-2.0.0_rc1-r6 reverts gcc to 3.4.5 from 4.1.1

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description Waldo 2006-06-18 23:58:46 UTC]

This took me FOREVER to track down.  The problem is that =app-admin/eselect-compiler-2.0.0_rc1-r6 forces gcc to go back to a previous version, namely 3.4.5 even when 4.1.1 has been selected via gcc-config

This makes such commands like "emerge -e system" mess up, because half the emerge is with gcc 4.1.1, and the other half is w/3.4.5.

This is a serious problem as it has affected subsequent builds and destablized my whole system.

I found a thread that discusses the problem:  http://forums.gentoo.org/viewtopic-t-471471-highlight-eselectcompiler.html

[Comment 1 Waldo 2006-06-19 00:16:54 UTC]

    I should probably explain how I tested this.

    # gcc-config 9
     * Switching native-compiler to x86_64-pc-linux-gnu-4.1.1 ...[ ok ]
    # gcc-config -l
     [1] x86_64-pc-linux-gnu-3.4.2
     [2] x86_64-pc-linux-gnu-3.4.2-hardened
     [3] x86_64-pc-linux-gnu-3.4.2-hardenednossp
     [4] x86_64-pc-linux-gnu-3.4.5
     [5] x86_64-pc-linux-gnu-3.4.5-hardened
     [6] x86_64-pc-linux-gnu-3.4.5-hardenednopie
     [7] x86_64-pc-linux-gnu-3.4.5-hardenednopiessp
     [8] x86_64-pc-linux-gnu-3.4.5-hardenednossp
     [9] x86_64-pc-linux-gnu-4.1.1 *
    # emerge eselect-compiler        
    .
    .
    .
    [it emerges]
    .
    .
    .
    # gcc --version
    x86_64-pc-linux-gnu-gcc (GCC) 3.4.5 (Gentoo 3.4.5, ssp-3.4.5-1.0, pie-8.7.9)
    Copyright (C) 2004 Free Software Foundation, Inc.
    This is free software; see the source for copying conditions.  There is NO
    warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

[Comment 2 Waldo 2006-06-19 00:26:11 UTC]

One last note:

# eselect compiler list

followed by

# eselect compiler set ##

(where ## equaled the new version)

Seems to have fixed this.  A subsequent emerge left gcc at 4.1.1.  There's nothing about this in the migration guides for gcc that I've seen, assuming this is the desired behavior.

W

[Comment 3 Jeremy Huddleston (RETIRED) 2006-06-20 02:18:20 UTC]

Did you source /etc/profile after you set the compiler with gcc-config-1.x and before you emerged eselect-compiler.  It sets the profile to the compiler being used to emerge it OR nothing if it doens't see a matching profile.  That means you were compiling it with 3.4 nad just forgot to . /etc/profile after your gcc-config.  Luckily, you don't need to source /etc/profile anymore with eselect-compiler =)

[Comment 4 Waldo 2006-06-20 13:25:24 UTC]

I swear I *did*  source /etc/profile .  When I did the update, I was on #gentoo-amd64 so I actually typed it twice, once in the terminal and once in irc.  I have no idea why it didn't do what it was supposed to...

W

[Comment 5 Jeremy Huddleston (RETIRED) 2006-06-20 14:54:35 UTC]

Ok, well I'll try to reproduce it, but I did test emerging eselect-compiler with 3.4 and 4.1 installed and with each one as the active compiler.  I'll try again, but it's working here...