View previous topic :: View next topic |
Author |
Message |
igoldtho n00b
Joined: 20 Apr 2003 Posts: 22
|
Posted: Sun Apr 20, 2003 1:56 am Post subject: error while loading shared libraries |
|
|
I had a power outage while installing a package and now when I run emerge sync (or emerge with any argument) I get this error.
/usr/bin/python2.2: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory
I get similar errors with startx and env-update (diferent libraries).
It seems that the problem should be a fairly simple one. I have checked that file "libstdc++.so.5" exists and is in the PATH - this is the limit of my expertise in such matters. Any help to avoid reinstalling will be appreciated. |
|
Back to top |
|
|
dwerg Tux's lil' helper
Joined: 30 Sep 2002 Posts: 101 Location: Amsterdam, the Netherlands
|
Posted: Sun Apr 20, 2003 2:15 am Post subject: |
|
|
Have you tried /sbin/ldconfig (as root)? |
|
Back to top |
|
|
igoldtho n00b
Joined: 20 Apr 2003 Posts: 22
|
Posted: Sun Apr 20, 2003 3:11 am Post subject: |
|
|
excellent! ldconfig seems to have rectified most of the problems (thank you!), however it generated the following errors when I ran it.
gentoo root # ldconfig
ldconfig: /usr/lib/libgconf-1.so.1.0.3 is not an ELF file - it has the wrong
magic bytes at the start.
ldconfig: /usr/lib/libgconf-1.so is not an ELF file - it has the wrong magic
bytes at the start.
ldconfig: /usr/lib/libgconf-1.so.1 is not an ELF file - it has the wrong magic
bytes at the start.
ldconfig: /usr/lib/libgconf-gtk-1.so is not an ELF file - it has the wrong
magic bytes at the start.
ldconfig: /usr/lib/libgconf-gtk-1.so.1 is not an ELF file - it has the wrong
magic bytes at the start.
ldconfig: /usr/lib/libgconf-gtk-1.so.1.0.0 is not an ELF file - it has the
wrong magic bytes at the start.
I am wondering whether Gentoo has a mechanism for verifying or reinstalling installed packages? |
|
Back to top |
|
|
dwerg Tux's lil' helper
Joined: 30 Sep 2002 Posts: 101 Location: Amsterdam, the Netherlands
|
Posted: Sun Apr 20, 2003 9:29 am Post subject: |
|
|
No, gentoo doesn't verify installs. You can do something like
. Type
to see it's outcome. Try
to see all the other options. There is also a portage howto on the documentation page: http://www.gentoo.org/doc/en/portage-user.xml |
|
Back to top |
|
|
murphy n00b
Joined: 01 Feb 2003 Posts: 21
|
Posted: Sun Apr 20, 2003 2:38 pm Post subject: |
|
|
I have a very similar problem. I was upgrading from 1.4rc2 to 1.4rc4. I was following the upgrade manual and was upgrading portage (emerge -u portage). I left for work, thinking all should be fine until I get back. I do, and I was kicked out of XWindows without any kind of error message (I guess I should have known not to do that but...). I tried starting portage's upgrading again and it gave me that error message about python2.2 (except it didn't have /usr/bin in front of it). I tried /sbin/ldconfig. It doesn't say anything, it just ran for a couple seconds and returned me to the command prompt. I tried emerge -up portage and it still gave me the same error message. I went to /usr/lib/gcc-lib/i686-pc-...-gnu/3.2.2/ and tried ldconfig -l libstdc++.so.5 and it said that it wasn't a regular file. I noticed that there was a libstdc++.so.5.0.2 and I tried the same thing with that. It seemed to run with no problem. So, I tried emerge -up portage again and it said the same error message. Any other ideas? Thanks for the help.
Glenn Murphy |
|
Back to top |
|
|
pjp Administrator
Joined: 16 Apr 2002 Posts: 20067
|
Posted: Sun Apr 20, 2003 5:59 pm Post subject: |
|
|
Moved from Installing Gentoo. _________________ Quis separabit? Quo animo? |
|
Back to top |
|
|
fountjas n00b
Joined: 24 Jan 2003 Posts: 3
|
Posted: Fri May 02, 2003 7:30 pm Post subject: |
|
|
I had a similar problem and managed to solve it !
first I did
Code: | ldconfig -v | grep libstdc |
There was nothing on my sick box, but on my working box got :-
Quote: | libstdc++.so.5 -> libstdc++.so.5.0.2 |
Then I check /etc/ld.so.conf and found the following line was missing on the sick box :-
Quote: | /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.2 |
I added the above line then just ran
as root, that seemed to fix it |
|
Back to top |
|
|
|