|
From: Bob R. <ra...@pa...> - 2009-02-14 03:02:03
|
I am trying to build visual python 5.0_candidate, on a linux
Ubuntu 8.0.4 (hard heron) laptop. I corrected an end-of-scope
problem at the end of render_manager.cpp (shown here:
-------------------------------------------------------------
*** src/core/util/render_manager.cpp.ORIG 2008-04-08 11:24:36.000000000 -0700
--- src/core/util/render_manager.cpp 2009-02-12 16:21:56.000000000 -0800
***************
*** 58,61 ****
return interval;
}
! } // namespace cvisual
\ No newline at end of file
--- 58,61 ----
return interval;
}
! } // !namespace cvisual
-------------------------------------------------------------------)
then got a complaint about the mutex_t type not containing a lock:
= - = - = - = - = - = - = - = - = = - = - = - = - = - = - = - = - = = - =
../../visual-5.0_candidate/src/core/util/render_manager.cpp:37: instantiated from here
../../visual-5.0_candidate/dependencies/threadpool/include/./threadpool/./detail/locking_ptr.hpp:50: error: ‘class boost::recursive_mutex’ has no member named ‘lock’
= - = - = - = - = - = - = - = - = = - = - = - = - = - = - = - = - = = - =
I haven't been doing any development in this environment, so I hope
there is a simple answer to what may be going wrong. I have attached
config.log and build.log, as requested in the make output.
I am using the "threadpool-0_2_5-src" threadpool source; I pulled
that down over a month ago, but I'm not sure whether that is the
right package. There are lock definitions in, e.g., the
/usr/include/boost/thread/detail/lock.hpp file, so there is the
possibility of picking out a lock definition. There was some
discussion in some file about which threadpool version to get for
use with visual python 5.0, and as I recall it wasn't totally
specific. So if this is just the wrong package, that would be an
easy answer.
Thanks for any help.
--Bob Rader |