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