1 |
On Mon, Aug 24, 2015 at 10:46 AM, Harry Putnam <reader@×××××××.com> wrote: |
2 |
> So, I've made the mess considerably worse... maybe unsolvable since I |
3 |
> have no gcc now and so no way to grind out the builds.... plus other |
4 |
> truly boneheaded uninstalls that appear to have rendered my system |
5 |
> unusable .... just like the little warning says when you |
6 |
> gentoo -vC pkg ....... wheeeeee. |
7 |
> |
8 |
|
9 |
Uh, not to drag you through the mud, but what gave you the idea to try |
10 |
that? I'm mainly interested so that we can go fix it if there is some |
11 |
document that is leading people astray. |
12 |
|
13 |
The suggestion was to check gcc-config -l, and then set a recent |
14 |
version of gcc if it isn't already selected. That should be the |
15 |
correct fix, though you might need to install a newer gcc version. |
16 |
You don't need to use emerge -C to do any of that. That command is |
17 |
one of those "I know what I'm doing" commands which will happily mess |
18 |
up your system. |
19 |
|
20 |
At this point your simplest solution is to create a binary package of |
21 |
whatever it is you got rid of and re-install it, but that is going to |
22 |
be a lot more complex than the minor issue you were having before. |
23 |
Your email is pretty light on details, so I don't even know what it |
24 |
was that you uninstalled. |
25 |
|
26 |
I'd suggest not doing stuff like this in the future. I can pretty |
27 |
much guarantee that emerge output like the one you posted will happen |
28 |
to you a few times a year and is fairly routine if you have a system |
29 |
with many packages on it. Granted, you won't have quite as much to |
30 |
deal with if you update daily/weekly, but still, you probably |
31 |
shouldn't go into panic mode everytime portage wants help with |
32 |
something because it happens fairly often. |
33 |
|
34 |
-- |
35 |
Rich |