1 |
On 9/7/06, michael@×××××××××××××.com <michael@×××××××××××××.com> wrote: |
2 |
> I'm upgrading my gcc from 3.x to 4.x. I've done the gcc switching, and now I'm |
3 |
> updating my system. |
4 |
> |
5 |
> The recommended steps are: |
6 |
> |
7 |
> # emerge -eav system |
8 |
> # emerge -eav world |
9 |
> |
10 |
> While emerging my system I received a message suggesting I run revdep-rebuild: |
11 |
> |
12 |
> warning - be sure to run revdep-rebuild now |
13 |
|
14 |
Um, I believe you can ignore this. The emerge -eav world will rebuild |
15 |
all packages...there is nothing that revdep-rebuild will catch that |
16 |
world won't. |
17 |
|
18 |
Now if you want to keep /using/ the system while it is rebuilding, you could do: |
19 |
|
20 |
emerge -eav system # if already complete, don't repeat |
21 |
revdep-rebuild --library libstdc++.so.6 |
22 |
emerge -eav world |
23 |
|
24 |
The revdep-rebuild command will recompile all C++ applications, and |
25 |
will take a damn long time to run. But less time than rebuilding |
26 |
world, and once it completes, your C++ apps should at least be sane. |
27 |
Otherwise you might get ABI conflicts while the world rebuild is going |
28 |
on. |
29 |
|
30 |
Of course, those same C++ apps are going to be rebuilt during the |
31 |
world step...which is kind of lame. There are some tricks you can use |
32 |
to avoid rebuilding things twice...search the archives of this list |
33 |
for ideas. |
34 |
|
35 |
-Richard |
36 |
-- |
37 |
gentoo-user@g.o mailing list |