Re: [gentoo-user] emerge --info

[Willie Wong <wwong@Princeton.EDU>]

On Mon, Sep 18, 2006 at 01:43:31PM -0700, Penguin Lover Richard Fish squawked:
> You really should follow the gcc upgrade guide [1], which tells you to:
> 
> source /etc/profile
> 

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

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

But on my desktop (which is on a hardened profile with x86 keyword)

3) gcc-config would successfully change the output of emerge --info

4) and 'eselect compiler' returns
"!!! Error: Can't load module compiler"
which is natural, since eselect-compiler is keyworded ~x86. 

Are those the intended behaviour? Or is something seriously wacked up?

W
-- 
Computer games don't affect kids, I mean if Pac Man affected us as kids, we'd 
be sitting around in darkened rooms munching pills and listening to repetitive
music.
Sortir en Pantoufles: up 24 days, 14:43
-- 
gentoo-user@gentoo.org mailing list