| 1 |
Ezequiel Garcia wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> I can't emerge any gcc. I tried emerging 4.7, 4.5.3-r2 with no luck. |
| 5 |
> |
| 6 |
> Should I file a bug? |
| 7 |
> |
| 8 |
> Thanks, |
| 9 |
> Ezequiel. |
| 10 |
|
| 11 |
|
| 12 |
I ran into this a while back and I had to do a emerge -e system then a |
| 13 |
emerge -e world. I'm not saying to do this yet but if no one posts a |
| 14 |
fix, you may have to try that route. |
| 15 |
|
| 16 |
In the meantime, make sure everything in make.conf is set correctly. |
| 17 |
Check for typos and other silly mistakes. Maybe post it here and see if |
| 18 |
someone else sees something. I don't even want to try to count the |
| 19 |
times all of us have had a typo that wrecks everything. |
| 20 |
|
| 21 |
Check gcc-config -l to make sure it is set. I have corrected issues in |
| 22 |
the past by changing it to a older gcc then back to the new one. I |
| 23 |
guess something got corrupted or something. It only takes a few |
| 24 |
seconds, it could be worth a try. Running env-update and source |
| 25 |
/etc/profile in between while at it. |
| 26 |
|
| 27 |
You can try revdep-rebuild to see if that helps but it may not. |
| 28 |
Sometimes you have to run that multiple times and check for mixing |
| 29 |
stable and unstable packages. There are occasions where mixing |
| 30 |
stable/unstable does not turn out to well. |
| 31 |
|
| 32 |
This is a common thing and I wouldn't file a bug report. It usually |
| 33 |
turns out to be a operator error or some setting that got messed up. |
| 34 |
|
| 35 |
Dale |
| 36 |
|
| 37 |
:-) :-) |
| 38 |
|
| 39 |
P. S. Hold on to your hair. No need to pull it out. lol |
| 40 |
|
| 41 |
-- |
| 42 |
I am only responsible for what I said ... Not for what you understood or |
| 43 |
how you interpreted my words! |
| 44 |
|
| 45 |
Miss the compile output? Hint: |
| 46 |
EMERGE_DEFAULT_OPTS="--quiet-build=n" |
Archives