1 |
On Tue, 2005-11-29 at 09:51 +0100, Gregorio Guidi wrote: |
2 |
> On Tuesday 29 November 2005 03:40, Mark Loeser wrote: |
3 |
> > Mike Frysinger <vapier@g.o> said: |
4 |
> > > that means when people upgrade to gcc-3.4, gcc-3.3 will remain on their |
5 |
> > > system until they remove it |
6 |
> > > |
7 |
> > > so if user fails to rebuild all their packages before unmerging gcc-3.3 |
8 |
> > > they will be screwed, but OH WELL |
9 |
> > |
10 |
> > Yea. Even after they remove it though, libstdc++-v3 should be pulled in |
11 |
> > after that. Only issue I really see is people that have libraries compiled |
12 |
> > with 3.3 and 3.4 and don't know why stuff is broken. I don't know how |
13 |
> > large of a problem that will be though. |
14 |
> |
15 |
> It will be huge, see |
16 |
> https://bugs.gentoo.org/show_bug.cgi?id=64615 |
17 |
> https://bugs.gentoo.org/show_bug.cgi?id=61146 |
18 |
> |
19 |
> Every user _must_ be instructed to run |
20 |
> 'revdep-rebuild --soname libstdc++.so.5', |
21 |
> if a system contains things linking to libstdc++.so.5 and things linking to |
22 |
> libstdc++.so.6 I consider it horribly broken. |
23 |
|
24 |
*sigh* |
25 |
|
26 |
...and when it tries to "recompile" openoffice-bin? doom3? |
27 |
|
28 |
A system linked against both libraries is definitely *not* broken, as |
29 |
there are plenty of cases where this is necessary. |
30 |
|
31 |
> Thus having libstdc++-v3 installed apparently solves a problem but in fact |
32 |
> does not solve anything, the only solution is to recompile everything c++ |
33 |
> related on the system. |
34 |
|
35 |
Except the binary apps that you don't have the source to be able to |
36 |
recompile. So now we're right back where we were, aren't we? |
37 |
|
38 |
-- |
39 |
Chris Gianelloni |
40 |
Release Engineering - Strategic Lead |
41 |
x86 Architecture Team |
42 |
Games - Developer |
43 |
Gentoo Linux |