Summary: | net-im/skype-2.2.0.25 - ./skype: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | tman <cornicx> |
Component: | New packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
tman
2011-05-29 02:30:20 UTC
Given skype being a binary package, it's a bad indicator of anything. If in the other packages error is similar, standard steps: check gcc-config, check ldd on the program. gcc-config seems to be ok. gcc-config 1 * Switching native-compiler to x86_64-pc-linux-gnu-4.5.2 ... nothing help: skype ./skype: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory i solved this problem with make manually the symblink. there must be sth wrong and should be fix. locate libstdc++.so.6 /usr/lib64/gcc/x86_64-pc-linux-gnu/4.5.2/libstdc++.so.6 /usr/lib64/gcc/x86_64-pc-linux-gnu/4.5.2/libstdc++.so.6.0.14 /usr/lib64/gcc/x86_64-pc-linux-gnu/4.5.2/32/libstdc++.so.6 /usr/lib64/gcc/x86_64-pc-linux-gnu/4.5.2/32/libstdc++.so.6.0.14 /usr/share/gdb/auto-load/usr/lib64/gcc/x86_64-pc-linux-gnu/4.5.2/libstdc++.so.6.0.14-gdb.py /usr/share/gdb/auto-load/usr/lib64/gcc/x86_64-pc-linux-gnu/4.5.2/32/libstdc++.so.6.0.14-gdb.py cd /lib32 lib32 # ln -s /usr/lib64/gcc/x86_64-pc-linux-gnu/4.5.2/32/libstdc++.so.6 libstdc++.so.6 Quite, but for the moment is seems to be wrong on your system only. If you don't know why it happened, it's likely to fall into WORKSFORME category. Same problem here with net-im/skype-2.2.0.35 , symlink fix it. I'm using Gentoo amd64 multilib. /usr/lib64/gcc/x86_64-pc-linux-gnu/4.5.2/32 should be listed in /etc/ld.so.conf or a file in /etc/ld.so.conf.d/ if it isnt, it should be listed in LDPATH in /etc/env.d/gcc/x86_64-pc-linux-gnu-4.5.2 if it isnt, then re-emerge sys-devel/gcc and see if the problem still persists (In reply to comment #6) > /usr/lib64/gcc/x86_64-pc-linux-gnu/4.5.2/32 should be listed in /etc/ld.so.conf > or a file in /etc/ld.so.conf.d/ > > if it isnt, it should be listed in LDPATH in > /etc/env.d/gcc/x86_64-pc-linux-gnu-4.5.2 > > if it isnt, then re-emerge sys-devel/gcc and see if the problem still persists yes, rebuilding gcc seems to have fixed the problem :) thanks for the suggestion. rebuilding gcc fixed the problem for me too. we need the full build log where the library was not installed in order to go anywhere |