Hi Michael, You need to make sure you don't have old libs hanging around, you will also need to make sure you don't mix 64 and 32 bit libs/executables. The OSG does version it's libs and the apps are built to match so it's usually quite hard to screw up and have problems, so there must be something odd in what you have done wr.t. OSG libs and builds.
Robert. On Sat, Jan 1, 2011 at 12:11 AM, Michael W. Hall <[email protected]> wrote: > That occurred to me. How do you use the ldd command? I will give that > a try and report back. > > I am thinking though that is may be the code. I am getting the same > problem with two separate machines. Both run Ubuntu 10.04 LTS. The > only difference is that one is 64 bit and the other is 32. The 32 is a > laptop and the 64 bit is a desktop. I have not had any trouble with osg > in a while. I do not get any compile errors, just the runtime error. > > > > On Mon, 2010-12-27 at 14:15 +0100, Alberto Luaces wrote: >> "Michael W. Hall" writes: >> >> > My bad. The error now states: >> > >> > osgversion: symbol lookup error: /usr/local/lib64/libosg.so.70: >> > undefined symbol: _ZN11OpenThreads5MutexC1ENS0_9MutexTypeE >> > >> > Ideas? >> >> It seems you are mixing libraries and executables from different OSG >> versions. Use the ldd command with osgversion in order to now which so's >> are picked for your system an environment. >> > > > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
