libstdc++.so.6

MylesCLin · 12-28-2004, 03:53 PM

When I try to run fluxbox after installing the latest package of it, it crashes and tells me it can't find libstdc++.so.6.
I can't seem to find this in slackware-current or anywhere else.
Can someone help me?

MylesCLin · 12-28-2004, 03:57 PM

Oh, and sorry for not putting this info up first, but I'm running a fresh install of Slackware 10.0.

MylesCLin · 12-28-2004, 04:11 PM

Oh, and sorry for not putting this info up first, but I'm running a fresh install of Slackware 10.0.
EDIT: Oops, it double-posted, sorry.

kostian · 12-28-2004, 05:09 PM

Hi.
http://www.slackware.com/changelog/stable.php?cpu=i386

Quote:

Mon Jun 14 00:39:32 PDT 2004
<snip>
a/cxxlibs-5.0.6-i486-1.tgz: Upgraded to libstdc++.so.5.0.6 from gcc-3.3.4.
No longer includes libstdc++.so.6 from gcc-3.4.0 -- this is pointless
since it won't work without the libgcc_s.so.1 from that version of gcc, and
we can't include that (the version in the gcc package would copy over it
if we tried). A possible solution would be for gcc to use unique library
versions for libgcc_s.so instead of making them all .so.1.

where did you get that package from? you could always build flux from source using checkinstall

__J · 12-30-2004, 08:27 PM

what version of gcc do you have installed? libstdc++ comes with g++ I have installed gcc-3.4.1 and have so.6 but I think gcc-3.2.x and 3.3.x have so.5. Rather than mess with this, It would probably be easier to get the source from -current and build it with the fluxbox.SlackBuild script.

I should add that if you use some prebuild binary packages, such as unrar and the prebuilt firefox packages, upgrading gcc to get libstdc++.so.6 will break these and building fulxbox from
source would be the best way to go.

v8dave · 01-01-2005, 05:13 AM

can someone tell me where the libstdc++.la file should list the library as being installed.

Mine says '/usr/lib/.' which seems to be giving me path problems with anything I compile.

__J · 01-01-2005, 06:52 AM

what kind of compiling problems? also, thats a static library so it should only give you problems if your passing --enable-static as configure params.