| 1 |
On Fri, 2005-12-02 at 03:03 +0100, Matthias Langer wrote: |
| 2 |
> On Thu, 2005-12-01 at 01:30 +0100, Marien Zwart wrote: |
| 3 |
> > On Wed, 30 Nov 2005 18:50:02 -0500 |
| 4 |
> > Mark Loeser <halcy0n@g.o> wrote: |
| 5 |
> > |
| 6 |
> > > Jakub Moc <jakub@g.o> said: |
| 7 |
> > > > 1.12.2005, 0:29:48, Chris Gianelloni wrote: |
| 8 |
> > > > revdep-rebuild --library=libstdc++.so.5 is all that's needed here to avoid |
| 9 |
> > > > things like Bug 64615. |
| 10 |
> > > |
| 11 |
> > > Yea, I updated my statement on the bug to reflect this. C++ stuff should be |
| 12 |
> > > the only thing affected, so this _should_ be enough. Its also already |
| 13 |
> > > something that's been in the ebuild for a while now. |
| 14 |
> > |
| 15 |
> > Not sure if everyone is aware of this, but most installed pythons link |
| 16 |
> > to libstdc++.so. This is not a problem if you run the above |
| 17 |
> > revdep-rebuild (it should catch it just fine). It is a problem if you |
| 18 |
> > get rid of gcc 3.3 before installing libstdc++-v3 or running the |
| 19 |
> > revdep-rebuild, as it will leave you with a broken python and therefore |
| 20 |
> > unable to emerge. |
| 21 |
> |
| 22 |
> How right you are; that just happend to me two days ago after removing |
| 23 |
> gcc-3.3.6 before emerge -e system on x86. Luckily it was a fresh |
| 24 |
> install ... |
| 25 |
|
| 26 |
But besides of this fact, which was my very own fault, i'm very happy |
| 27 |
with gcc-3.4. I thought, that maybe some c++ packages would fail to |
| 28 |
compile, as I'm a c++ devel myself and know that there are differneces |
| 29 |
in the c++ code that gcc-3.3.x and gcc-3.4.x are accepting. However, I'm |
| 30 |
running gcc-3.4 now on 2 of 3 gentoo boxes i'm mentaining and are very |
| 31 |
pleased with the results. |
| 32 |
|
| 33 |
matthias |
| 34 |
|
| 35 |
> |
| 36 |
> matthias |
| 37 |
> > |
| 38 |
> > -- |
| 39 |
> > Marien. |
| 40 |
> |
| 41 |
|
| 42 |
-- |
| 43 |
gentoo-dev@g.o mailing list |
Archives