Re: [gentoo-user] Why does my system still want gcc 3.4.9?

[Volker Armin Hemmann]

On Mittwoch, 14. Mai 2008, felix@×××××××.com wrote:
> I have been battling this weirdness for several months, and it has
> been getting worse and worse.  Now I can't even unpack half the man
> pages.
>
> The short of it is that a lot of binaries on my system are linked
> against gcc 3.4.9, even if I remerge them from scratch.  It happened
> with gcc 4.2.2, I emerged 4.2.3 and it still happens.  The most common
> broken binary is /usr/bin/lzma, which I have remerged several times
> since the 4.2.3 emerge to no avail.
>
> # ldd /usr/bin/lzma
> /usr/bin/lzma: /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/libstdc++.so.6: version
> `GLIBCXX_3.4.9' not found (required by /usr/bin/lzma) linux-gate.so.1 =>
> (0xffffe000)
>         libstdc++.so.6 =>
> /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/libstdc++.so.6 (0xb7e3a000) libm.so.6
> => /lib/libm.so.6 (0xb7e15000)
>         libgcc_s.so.1 => /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/libgcc_s.so.1
> (0xb7e09000) libc.so.6 => /lib/libc.so.6 (0xb7cd4000)
>         /lib/ld-linux.so.2 (0xb7f63000)
>
> gcc-config is happy:
>
> # gcc-config -l
>  [1] i686-pc-linux-gnu-4.1.2
>  [2] i686-pc-linux-gnu-4.2.3 *
>
> The bad symlinks for gcj components (reported by revdep-rebuild) have
> been fixed.
>
> There is an old gcc hanging around, which I have been tempted to move
> out of the way and see what happens, but I don't like broken
> unbootable systems.
>
> $ ll /usr/lib/gcc/i386-pc-linux-gnu/
> total 0
> drwxr-xr-x 2 root root 80 Jun 12  2006 3.4.4
>
> with the other two versions elsewhere:
>
> $ ll /usr/lib/gcc/i686-pc-linux-gnu/
> total 4
> drwxr-xr-x 4 root root 2464 Dec 27 15:07 4.1.2
> drwxr-xr-x 5 root root 2504 May 12 11:58 4.2.3
>
> This is a ~x86 system.

there are/were probably a bunch of *la files left which have that stale crap 
in them. Grep for it. Then remove them.

-- 
gentoo-user@l.g.o mailing list