ActiveState Powered by ActiveState

ActiveState Community


Komodo Personal Trial install on Linux

Posted by tropis on 2007-01-20 15:40

Hi!
Error message::
> ./install.sh
./INSTALLDIR/lib/python/bin/python2.4: error while loading shared libraries:
libstdc++.so.5: cannot open shared object file: No such file or directory

Yes I see discussion about libstdc++.so versions in the README:

...
Two packages, based on different C++ libraries, are available for both
Komodo Professional and Komodo Personal:

* The libcpp3 package: built for libstdc++ version 3 (Red Hat 7.x and 8.x)
* The libcpp5 package: built for libstdc++ version 5 (Red Hat 9.x, Red
Hat Enterprise Linux 3, SuSE 8.x and 9.x, Fedora)

Choose the distribution that corresponds to your version of libstdc++.
To check which version of libstdc++ is installed on your machine, run
the following command:
ls /usr/lib/libstdc++*
If libstdc++.so.5 appears in the output, install the libcpp5 version. If
not, install the libcpp3 version.
...

On my Fedora Core 6 system, I get this:
> ls /usr/lib/libstdc++*
/usr/lib/libstdc++.so.6@
/usr/lib/libstdc++.so.6.0.8*

So I don't mind specifying some other library, but I don't see any docs
about how to do that. install.sh -h does nothing either
thx!-rob

chmac | Mon, 2007-01-22 08:31

Hey Tropis,

I had the same problem on FC6. I did a `locate libstdc++` and discovered libstdc++.so.5 is installed as part of VMWare Server. However, if you don't have VMWare server installed, I'm not sure where you'd get the file. I just did a quick search yum and I can't see it in any of the libstdc packages.

I think you can download and unpack vmware without installing it, but a 100Mb download for a 1mb lib does seem a little over the top! :)

Good luck - Callum.

kevinw | Fri, 2007-01-26 12:27

Hello folks,

That behaviour was a bug in a beta of Komodo. If you download and use a current (release) version of 4.0 you won't run into that problem.

libstdc++.so.5 is part of one of the "compat" RPMs for FC6, if I remember correctly. Searching for the filename on rpmfind or a similar service should turn up the proper RPM name.

Cheers,

kjw

-->