After upgrading gcc, libstdc++.so.5 no longer exists

evoweiss

Hi all,

I just updated from glibc-2.3.4.20040808-r1 to glibc-2.3.4.20041102-r1. I emerged it with a script that rebuilds the toolkit.

After the whole process was through, most of my applications stopped working. The common error is as follows:

paladin-zero · Guru Joined: 19 May 2004 Posts: 322

Thats interesting. After updating glibc this morning, I also do not have libstdc++.so.5 in /usr/lib, but revdep-rebuild didnt find a package that complained about it. Maybe I didnt have that library before the update. I am able to run my programs, such as mplayer.

Maybe your problem was exacerbated by running the emrg-wrapper.sh script? (mentioned in a related thread)

evoweiss · Posted: Wed Mar 16, 2005 4:31 pm Post subject:

Hi again,

paladin-zero · Guru Joined: 19 May 2004 Posts: 322

I have 3.3.5-r1

evoweiss · Posted: Wed Mar 16, 2005 4:37 pm Post subject:

NiLuJe · Posted: Wed Mar 16, 2005 5:04 pm Post subject:

I think the problem comes from a change in the toolchain eclass (wich seems to have been updated today ^^) ... I only recompiled gcc, and had the same problem .. I found out that for some reason (is_cxx test failing? Another thing?) Emerge/Portage wasn't adding ',c++' to the --enabled-languages option of gcc's configure .. (I ended up hardcoding the var GCC_LANG to 'c,c++' instead of 'c' in the toolchain eclass .. Ugly 'workaround' :/ )

(btw, I'm using gcc-3.4.3-20050110)

evoweiss · Posted: Wed Mar 16, 2005 5:10 pm Post subject:

Hi,

NiLuJe · Posted: Wed Mar 16, 2005 5:13 pm Post subject:

I simply changed

evoweiss · Posted: Wed Mar 16, 2005 5:20 pm Post subject:

Hi,

jonaswidarsson · Posted: Wed Mar 16, 2005 5:24 pm Post subject:

Are/were you as I missing the g++ binary?
I have this post explaining my problem.
I will try the suggestion NiLuJe made above as soon as the current gcc emerge is finished, and I discover it didn't work...

evoweiss · Posted: Wed Mar 16, 2005 5:27 pm Post subject:

Hi,

I was wondering, have you posted this problem to the gentoo bugtracker yet? If not, perhaps it'd be worth doing.

Best,

Alex

evoweiss · Posted: Wed Mar 16, 2005 5:38 pm Post subject:

Ok... I really fscked things up during the re-emerge of a lower version of glibc, bad things happened (can't log into the system remotely and right before it happened, doing something as simple as ls led to a segault).

I have a copy of the livecd. I imagine that the main thing I need to do is to boot from it, chroot, and then re-emerge the correct version of the offending package. Is that right?

Best,

Alex

NiLuJe · Posted: Wed Mar 16, 2005 5:47 pm Post subject:

jonaswidarsson > Yes, since it was skipping all c++ support, it wasn't building g++

evoweiss > Awww :/ Good Luck!

jonaswidarsson · Posted: Wed Mar 16, 2005 5:51 pm Post subject:

roymaster · n00b Joined: 05 Jan 2003 Posts: 64 Location: Europe

NiLuJe · Posted: Wed Mar 16, 2005 5:57 pm Post subject:

No bug filed, I'm not registered at gentoo's bugzilla, if someone around here could do it, i'd like that, saves me some time ^^

jonaswidarsson · Posted: Wed Mar 16, 2005 6:13 pm Post subject:

Well, I can tell it worked.

Just one more little special tricky thing.
python needs libstdc++.so.5. So to get emerge going I need that one, and I didn't have it.
So I made a symlink (earlier today) :

jonaswidarsson · Posted: Wed Mar 16, 2005 6:28 pm Post subject:

Well, my theory was a little wrong.
libstdc++.so.5 shouldn't be in /usr/lib at all.
it should be here:
/usr/lib/gcc-lib/i586-pc-linux-gnu/3.3.5/libstdc++.so.5

and it probably already was, but since I had a symlink in the way when checking for libraries kopete failed to start complaining about it couldn't get version info, due to my crazy link.

But indeed I needed it to make portage run.
And my trick was actually successful.
Now all is fine over here.

I suggest someone with a little experience of the inner workings of portage file the bug report. I am not well enough experienced.

evoweiss · Posted: Wed Mar 16, 2005 6:48 pm Post subject:

Hi all,

Looks like a bug has been posted and a patch is out. Follow this link.

I'm in the midst of a painful process, thanks for your good wishes!

Best,

Alex

NiLuJe · Posted: Wed Mar 16, 2005 6:51 pm Post subject:

Yeah, i had the same kind of problem .. ^^

Except that I use gcc-3.4.3, so it was libstdc++.so.6 ^^

I had to google (with a browser wich didn't got killed, hopefully ^^ But I guess it should work with something like links or lynx ...) 'gcc-<myversion>.tbz2' to get a binary version of gcc (Beacause I had just deleted mine .. -_- Silly me ^^), extracted it, and copied the libstdc++.la, libstdc++.a (I don't think these static library are really needed in this case, but, why not? ^^) & libstdc++.so.x.y.z (6.0.3 for me) from the package in the right place on my / [/usr/lib/gcc-lib/i686-pc-linux-gnu/<my-gcc-version>/], and made the symlinks (lstdc++.so , lstdc++.so.x, and finally launched ldconfig

EDIT : Thanks for the link to the bug

Seems that there is a cleaner fix for this issue

HiTech69 · Posted: Wed Mar 16, 2005 8:01 pm Post subject:

HiTech69

I posted this issue as a reply to someone having a similar problem, but in hopes of expediting a fix on my paralyzed box, here's a post by itself.

Was doing an emerge -uDv system this morning, and surprised to see gcc and glibc complie so cleany without errors, however, about 6 packages later python croaked and gave this error:

Maedhros

HiTech69

Maedhros