On 9/18/06, Willie Wong <[EMAIL PROTECTED]> wrote:
I did follow the guide and did source /etc/profile. I just forgot to type that step in in composing the e-mail. And I have a .bash_history to back me up ;p
Sorry, although we aren't psychic, so we can only base responses on what you _actually_ put in your email. ;-]
I did a bit of experimentation, actually, and found that the behaviour is different on my laptop and on my desktop. On my laptop where this problem originates (default-linux profile and ~x86 keyword): 1) no matter what I do with gcc-config (and sourcing /etc/profile afterwards of course), the emerge --info gives the same compiler. 2) To actually affect the emerge --info I need to use 'eselect compiler set', i.e. now that I issued 'eselect compiler set 6', my emerge --info reads correctly Portage 2.1.2_pre1 (default-linux/x86/2006.0, gcc-4.1.1/vanilla
eselect compiler should not work *anywhere* as eselect-compiler is currently package masked for everybody [1]. -Richard [1] http://bugs.gentoo.org/show_bug.cgi?id=143697 -- gentoo-user@gentoo.org mailing list
