Re: [gentoo-user] ~x86 emerge: broke emerge
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 message you are. i did a locate for it (and then subsequently all the other libs it couldnt find) and copied them manually to /usr/bin. i didnt think to try ldconfig or anything like that so im not sure. but since then i have upgraded gcc again and everythings worked perfectly. one side affect you may notice if you tried starting gnome from the command prompt would be that nautilis didnt start even after you fixed the problem. im not sure why but just running it once from a terminal and everything went back to normal (normal being that nautilis starts with gnome again). ive been using ~x86 for maybe 2 weeks now and that was my first encounter. just remember. switching back to x86 isnt the easiest thing to do. and besides - there are too many benifits to living on the edge. constant heart failure is one of them ;) currently im having problems with openoffice-ximian but i think its related to trying to run 5 parallel makes (the changelog says something about parallel makes not playing nice) and pwlib wont compile either. other than that im much happier in ~x86. have fun, Frank J. Mattia Kurt Guenther wrote: 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 -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] ~x86 emerge: broke emerge
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 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 with ls). If so, do export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:" and you should be able to use emerge (from the terminal(s) on which you executed the export command). Then I would suggest reverting to a stable emerge ASAP... If libstdc++.so.5 is indeed missing, gcc has to be reinstalled as Spider pointed out. Prepare for some work... And, as a side note, never ever use an emerge -d without emerge -dp first (and putting all you can't afford to lose in /var/cache/edb/world)! -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] ~x86 emerge: broke emerge
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, christoph -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] ~x86 emerge: broke emerge
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 with ls). If so, do export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:" and you should be able to use emerge (from the terminal(s) on which you executed the export command). Then I would suggest reverting to a stable emerge ASAP... If libstdc++.so.5 is indeed missing, gcc has to be reinstalled as Spider pointed out. Prepare for some work... And, as a side note, never ever use an emerge -d without emerge -dp first (and putting all you can't afford to lose in /var/cache/edb/world)! -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] ~x86 emerge: broke emerge
-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 a way to fix emerge? The file 'missing' is part of gcc! What does your '/etc/ld.so.conf' contain? And what version of gcc are you running? - -- Mike Williams -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFAIXfkInuLMrk7bIwRAjyTAJ9aocgScim2+Cdn4/aL31d6uUhbmACdFees WrziQ2ZMqQTTYZd6k6JCn1o= =PfN0 -END PGP SIGNATURE- -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] ~x86 emerge: broke emerge
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 fix emerge? Might be. run "ldd /usr/bin/python" and see. usually it will look for libstdc++ which is part of gcc. the fact that its missing from your system is alarming. look inside : /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/libstdc++.so.5 of course, the gcc version (here 3.3.2) will probably be different. as the CHOST ( 686-pc-linux-gnu ) might be. if other versions of libstdc++ is in that dir, make a symlink. if not, ouch. if you have unmerged gcc, you're in trouble. Grab a binary gcc (http://chinstrap.alternating.net has one grp set, or the old 1.4 grp's, or the stage2 or 3 tarballs) and copy to your system, then rebuild gcc. Nothing is impossible to fix, some things hurt a bit though. //Spider -- begin .signature This is a .signature virus! Please copy me into your .signature! See Microsoft KB Article Q265230 for more information. end pgp0.pgp Description: PGP signature
[gentoo-user] ~x86 emerge: broke emerge
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
