| 1 |
On Tuesday 29 November 2005 03:40, Mark Loeser wrote: |
| 2 |
> Mike Frysinger <vapier@g.o> said: |
| 3 |
> > that means when people upgrade to gcc-3.4, gcc-3.3 will remain on their |
| 4 |
> > system until they remove it |
| 5 |
> > |
| 6 |
> > so if user fails to rebuild all their packages before unmerging gcc-3.3 |
| 7 |
> > they will be screwed, but OH WELL |
| 8 |
> |
| 9 |
> Yea. Even after they remove it though, libstdc++-v3 should be pulled in |
| 10 |
> after that. Only issue I really see is people that have libraries compiled |
| 11 |
> with 3.3 and 3.4 and don't know why stuff is broken. I don't know how |
| 12 |
> large of a problem that will be though. |
| 13 |
|
| 14 |
It will be huge, see |
| 15 |
https://bugs.gentoo.org/show_bug.cgi?id=64615 |
| 16 |
https://bugs.gentoo.org/show_bug.cgi?id=61146 |
| 17 |
|
| 18 |
Every user _must_ be instructed to run |
| 19 |
'revdep-rebuild --soname libstdc++.so.5', |
| 20 |
if a system contains things linking to libstdc++.so.5 and things linking to |
| 21 |
libstdc++.so.6 I consider it horribly broken. |
| 22 |
|
| 23 |
Thus having libstdc++-v3 installed apparently solves a problem but in fact |
| 24 |
does not solve anything, the only solution is to recompile everything c++ |
| 25 |
related on the system. |
| 26 |
-- |
| 27 |
gentoo-dev@g.o mailing list |
Archives