libstdc++.so.6: version `GLIBCXX_3.4.9' Please Help
 

Hello,
Using swaret, I upgraded my Slackware 12.1 machine with a host of new packages to bring it to current, and am now having library versioning issues.

An example of what I am now getting when I try to run 'lisa'

Another problem I am having now is that my system has a KDE startup ArtsServer Crash and I now cannot start the KDE sound system.
I have re-run alsaconf and it detected the soundcard fine but after the upgrade, there are no Sound devices listed in:
Control Center ==> Sound & Multimedia ==> Sound System ==> Hardware ==>
Select the audio device.

Beep Media Player also does not start now (even when running it in a console, I get no output whatsoever, so I am at a loss as to how to fix it, strangely Amarok still plays without problems??).

Would all of these issues be related to the same libstdc++ library?
If so, what version and what package supplies the correct GLIBCXX_3.4.9 version?

I have run 'swaret --dep', but swaret says that there are no missing dependencies.

Is there any other method apart from swaret for determining what is actually wrong with my system?

Can anyone suggest which package(s) && what version(s), I need to downgrade/remove/install to resolve these library and sound issues, so that I can get my system back to it's former working state.

I'm a bit lost, so I thank you for any assistance.

Cheers

Orbit

Did you upgrade gcc and cxxlibs?
The strange thing is that it finds the libstdc++.so under /lib, while it should be under /usr/lib. Run
to see where the symlink points. If you have /usr/lib/libstdc++.so.6 then you can move the /lib/libstdc++.so.6 in /tmp, run ldconfig and see if your program (lisa) works.

There's literally nothing in -current that isn't available as simple patches for Slackware 12.1 as far as I can tell, so I don't know WHAT you did to your system. An "upgrade" from 12.1 to current should upgrade all of 5 (max. 7 if you use some stuff in extra/) packages, none of which affect gcc, cxxlibs or glibc. This is precisely the reason I don't use automated tools to upgrade things...

Please describe your 'upgrade' procedure in more detail. Did you do it in runlevel 1? What commands did you use? What packages were upgraded, changed, etc? I hope swaret has logs in case you forgot. If you do system backups you could possibly restore your files or at least compare the contents of /var/log/packages to see what changes you made.

If you cannot do anything of these things my recommendation is that you downgrade back to 12.1 (without swaret).

You might be able to fix random problems like this particular library problem, but you wouldn't have these kinds of random problems if your system had been upgraded properly.

Hello All,

First up, thank you all very much for your responses.

I have resolved the library issue I was having.

What I did was to find on the internet the correct version of libstdc++-6.0.9 that my system wanted, and then copy it and symlink it in /usr/local/lib.

After ldconfig'ing my system, everything is happy again.

I think this may have been caused by the fact that my system is an upgrade of 12.0 and there are programs installed that I had previously compiled on earlier versions of Slackware.

Swaret seems to have upgraded everything correctly but one of my symlinks got directed to a different version of the library after installing the newer package versions and this caused the problem.

I'll look out for this little trap in the future.

Cheers

Orbit

Putting your library symlinks under /usr/local/lib is not necessarily the best solution. Keep in mind that those links are there when you do future upgrades/package management.

You never told us before that your upgrade was from 12.0, but I honestly figured it was seeing the problems you are having. I recommend you read this Upgrade HowTo. Even if you don't think you need it now, it will give you an idea of how to have more successful upgrades in the future.

Hello shadowsnipes,

Thanks for the link, I'll look into it.

Cheers

Orbit