1 |
On Sat, 27 May 2006, Neil Bothwick wrote: |
2 |
|
3 |
> On Sat, 27 May 2006 07:54:44 +0200, Alexander Skwar wrote: |
4 |
> |
5 |
> > > and KDE continued to |
6 |
> > > work. |
7 |
> > |
8 |
> > Not here. |
9 |
> |
10 |
> I've had a few strange errors since posting that. Like one from Konqueror |
11 |
> when trying to load a page, which then loaded perfectly on the next try. |
12 |
> |
13 |
> > > Maybe i've not run one of the affected programs. |
14 |
> > |
15 |
> > > Re-emerging |
16 |
> > > *everything* to fix a KDE problem seems like knee-jerk overkill. |
17 |
> > |
18 |
> > Well, but that's what's suggested. |
19 |
> |
20 |
> I think I'll pass on that one. Rebuilding all of KDE will take long |
21 |
> enough, but it seems prudent, I'm certainly not going to spend 16+ hours |
22 |
> rebuilding OOo if I don't need to. |
23 |
> |
24 |
> > Anyway, it's plain wrong that NOTHING has to be done after upgrading |
25 |
> > to gcc 4.1.1. Maybe an "emerge -e world" is required. And an "emerge |
26 |
> > -e world" is *very* *much* from doing nothing... |
27 |
> |
28 |
> Absolutely. The GWN posting was clearly optimistic :( |
29 |
> |
30 |
> |
31 |
|
32 |
Why would an emerge -e world be required? It is not required to rebuild |
33 |
every package using the new gcc. They will slowly be rebuilt when they are |
34 |
upgraded. I have done nothing since upgrading and had not one issue. Why |
35 |
would I, it doesn't even make sense? They are binaries, after all. |
36 |
-- |
37 |
gentoo-user@g.o mailing list |