Am Mittwoch, 14. Mai 2008 schrieb ext [EMAIL PROTECTED]: > 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.
There is no such thing as gcc 3.4.9.
> 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)
You emerged it with 4.2.3, but _at_runtime_ it's trying to get libstdc++
from 4.1.2. Check your environment, especially all variables with PATH in
their name (env|grep PATH), as well as /etc/ld.so.conf.
Try: LD_LIBRARY_PATH=/usr/lib/gcc/i686-pc-linux-gnu/4.2.3 ldd /usr/bin/lzma
If this works, try running "env-update && source /etc/profile", then
just "ldd /usr/bin/lzma" again.
> gcc-config is happy:
It doesn't matter how happ gcc-config is. Your runtime linker is not.
> 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.
Rename it and run revdep-rebuild. If everything is fine you can remove it.
HTH...
Dirk
--
Dirk Heinrichs | Tel: +49 (0)162 234 3408
Configuration Manager | Fax: +49 (0)211 47068 111
Capgemini Deutschland | Mail: [EMAIL PROTECTED]
Wanheimerstraße 68 | Web: http://www.capgemini.com
D-40468 Düsseldorf | ICQ#: 110037733
GPG Public Key C2E467BB | Keyserver: wwwkeys.pgp.net
signature.asc
Description: This is a digitally signed message part.
