On Monday 13 August 2007 07:02, Andreas Niederl wrote:
> Hi,
>
> Iain Buchanan wrote:
> > Hi all,
> >
> > another gcc upgrade issue :)  I've read and followed the gcc upgrade
> > gentoo howto, and also a few bugs on b.g.o, but I'm getting stuck...
> >
> > this all went well:
> > # gcc-config i686-pc-linux-gnu-4.1.2
> > # env-update && source /etc/profile
> > # fix_libtool_files.sh 3.4.6
> > # emerge --oneshot -av libtool
> >
> > then I did an emerge -eav system, also went well.
> >
> > Then I started upgrading, but came into this error:
> >
> > /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libstdc++.so.6: version
> > `CXXABI_1.3.1' not found
> >
> > so I ran `revdep-rebuild --library=libstdc++.so.6` but that got stuck on
> > eix:
> >
> > src/eix: /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libstdc++.so.6: version
> > `CXXABI_1.3.1' not found (required by src/eix)
> >
> > libstdc++so.6 belongs to gcc 3.4.x, so I recompiled gcc 4.1.2 just in
> > case, and then re-ran the entire above sequence, but it gets stuck again
> > at the same place.  libstdc++so.6 _still_ belongs to gcc 3.4.x.  Is this
> > a problem?
>
> [...]
>
> Unmerging the old gcc should take care of this.

That's what I thought, but then noticed this:
==============================================
# gcc-config -l
 [1] i686-pc-linux-gnu-3.4.5
 [2] i686-pc-linux-gnu-3.4.5-hardened
 [3] i686-pc-linux-gnu-3.4.5-hardenednopie
 [4] i686-pc-linux-gnu-3.4.5-hardenednopiessp
 [5] i686-pc-linux-gnu-3.4.5-hardenednossp
 [6] i686-pc-linux-gnu-4.1.2 *

# emerge -C -p -v gcc

>>> These are the packages that would be unmerged:


!!! 'sys-devel/gcc' is part of your system profile.
!!! Unmerging it may be damaging to your system.


 sys-devel/gcc
    selected: 4.1.2 
   protected: none
     omitted: none

>>> 'Selected' packages are slated for removal.
>>> 'Protected' and 'omitted' packages will not be removed.
==============================================

So gcc-3.4.5 is no longer in my system, but gcc-config tells me that it is 
available. Don't know what to make of this.  BTW I do not suffer (yet) from 
the same problem like the OP.
-- 
Regards,
Mick

Attachment: pgpA6qMHO6jFI.pgp
Description: PGP signature

Reply via email to