i had this problem about a week ago. emerging gcc for the first time
after switching to ~x86 resulted in something happening where many of
the g++ libs that are usually (iirc - im not at my computer right now)
put in /usr/lib/ were not there. basically i was getting the exact same
error messa
It broke on a "emerge world". I haven't deleted anything for some time.
I found the shlib, so I put it on my LD_LIBRARY_PATH. Much better!
I'll go back to the relative safety of X86.
--Kurt
Arne Vogel wrote:
Kurt Guenther wrote:
tumbleweed root # emerge
/usr/bin/python: error while loadin
Kurt Guenther wrote:
tumbleweed root # emerge
/usr/bin/python: error while loading shared libraries: libstdc++.so.5:
cannot open shared object file: No such file or directory
tumbleweed root #
I just emerged gcc-3.3.2-r6 and got the same error.
Is there a way to fix emerge?
run ldconfig
bye, chr
Kurt Guenther wrote:
tumbleweed root # emerge
/usr/bin/python: error while loading shared libraries: libstdc++.so.5:
cannot open shared object file: No such file or directory
tumbleweed root #
Try to 'locate libstdc++.so.5' and see if it's still there (the locate
DB could be outdated, so verify
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 04 February 2004 22:06, Kurt Guenther wrote:
> tumbleweed root # emerge
> /usr/bin/python: error while loading shared libraries: libstdc++.so.5:
> cannot open shared object file: No such file or directory
> tumbleweed root #
>
>
> Is there
begin quote
On Wed, 04 Feb 2004 17:06:01 -0500
Kurt Guenther <[EMAIL PROTECTED]> wrote:
> tumbleweed root # emerge
> /usr/bin/python: error while loading shared libraries: libstdc++.so.5:
>
> cannot open shared object file: No such file or directory
> tumbleweed root #
>
>
> Is there a way to
tumbleweed root # emerge
/usr/bin/python: error while loading shared libraries: libstdc++.so.5:
cannot open shared object file: No such file or directory
tumbleweed root #
Is there a way to fix emerge?
--Kurt
--
[EMAIL PROTECTED] mailing list
