Solved. Running ldd proved a great help. Long story short, I have to
change the links. So, instead of
ln -s libboost_thread-gcc41-mt-1_39.so.1.39.0 libboost_thread-mt.so, I
had to change the link to
ln -s /full/path/to/libboost_thread-gcc41-mt-1_39.so.1.39.0
libboost_thread-mt.so and it works now. Thanks for all the help and
advice
On Thu, Jul 16, 2009 at 11:35 AM, Vladimir
Prus
Kishalay Kundu wrote:
The __vdso_clock_gettime problem seems to exist in the .a version. It doesn't show up when I build a shared library (libxfem.so) that is then loaded on runtime by a driver. This shared library has a class that contains boost threads. The error occurs when I construct a local thread (code snippet below). I do not know what the etiquette for attaching code files on boost mailing list is, so I'm not attaching my codes. But if you wish, I can send you the code files.
boost::thread st( &XFE_Scene::run, _scene ); // error occurs here _threads[ 0 ] = boost::move( st );
When I try to load libxfem.so at run time, this is the error that I get.
/home/kish1/Projects/Ashwini2.0/trunk/Engine/SafeDriver/src/CoreManager.cpp@initialize,82: fatal error: could not open libxfem.so /home/kish1/Projects/lib/libxfem.so: undefined symbol: _ZTIN5boost6detail16thread_data_baseE
This can mean that either:
1. You libxfem.so does not actually link to Boost. 2. Or, at runtime, a different version of Boost libraries is getting picked up. Running ldd on /home/kish1/Projects/lib/libxfem.so might help.
- Volodya
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users