1 |
Neil Bothwick wrote: |
2 |
> On Fri, 26 May 2006 22:31:18 +0200, Alexander Skwar wrote: |
3 |
> |
4 |
>> > No, see this weeks Gentoo Weekly Newsletter. |
5 |
>> > |
6 |
>> > "To upgrade to the new version (assuming you are using gcc-3.4), all |
7 |
>> > that is required is to upgrade GCC and then select the new profile |
8 |
>> > using gcc-config." |
9 |
>> |
10 |
>> Wrong. An "emerge -e world" is required, if certain packages (like |
11 |
>> qt) get compiled after having switched to gcc 4.1.1. See |
12 |
>> https://bugs.gentoo.org/show_bug.cgi?id=134447 |
13 |
> |
14 |
> I needed to run fix_libtool |
15 |
|
16 |
fix_libtool wasn't enough to get KDE stuff working again. I needed |
17 |
to recompile. |
18 |
|
19 |
> to get the new kdelibs update to compile. But |
20 |
> I re-emerged qt, so I could try kdehiddenvisibility |
21 |
|
22 |
That's what I did and then KDE broke. As flameeyes wrote in the cited bug: |
23 |
|
24 |
| We can't really do much, when you rebuilt qt3 and qt4 you made a two-versions |
25 |
| linkage of libstdc++. Re-emerge of world is suggested. |
26 |
|
27 |
> and KDE continued to |
28 |
> work. |
29 |
|
30 |
Not here. |
31 |
|
32 |
> Maybe i've not run one of the affected programs. |
33 |
|
34 |
> Re-emerging |
35 |
> *everything* to fix a KDE problem seems like knee-jerk overkill. |
36 |
|
37 |
Well, but that's what's suggested. |
38 |
|
39 |
Anyway, it's plain wrong that NOTHING has to be done after upgrading |
40 |
to gcc 4.1.1. Maybe an "emerge -e world" is required. And an "emerge |
41 |
-e world" is *very* *much* from doing nothing... |
42 |
|
43 |
Alexander Skwar |
44 |
-- |
45 |
<dark> Turns out that grep returns error code 1 when there are no matches. |
46 |
I KNEW that. Why did it take me half an hour? |
47 |
-- Seen on #Debian |
48 |
-- |
49 |
gentoo-user@g.o mailing list |