From: Ari H. <ahe...@an...> - 2001-03-28 20:13:19
|
On Tue, 27 Mar 2001, Andrew Morrison wrote: > Finally, after I could not get libstdc++ upgraded or changed to the right > version anymore, I gave up and installed via rpm with --nodeps. Ennnt! You lose ;) You *must* install visual with the correct libstdc++ version. The libstdc++ version is specified in the dynamic dependencies of the Visual library, cvisualmodule.so: nimrod:~/cvs/cvisual$ ldd cvisualmodule.so ... libstdc++-libc6.2-2.so.3 => /usr/lib/libstdc++-libc6.2-2.so.3 (0x406b5000) ... You must find the package on rpmfind and install it. It lists itself as being in the libstdc++2.10-glibc2.2 package on this machine. I'm sure the version on RH is at least a few versions behind that. It looks like RH 7 has changed their naming scheme and are calling the package libstdc++-2.69-69.rpm. > > Then I found out I was using python1.5, which the webstie said not to do, > so I went out and got python2.0 after getting that installed, I tried to > uninstall the python-visual rpm and the python-15. rpm and reinstall > visual-python with the new version of python. That's the website being unclear. We removed all the Python-2 syntax in Visual; it now works in python 1.5.2, and the Linux packages expect to run on top of 1.5.2. > > It didn't work. Maybe I'm not using rpm correctly. Any help would be > greatly appreciated since I love vpython on my winows machine at home, I'd > like to use it in the office at school, too. > I apologize for this being a mess. You're welcome to get the source and build it yourself; putting it in place is not too unstraightforward and it will solve your library versioning problems. I run debian, and i can't keep around machines for 3 or 4 RH versions just to produce VPython packages for them. Ari |