Hi Vicente: Thanks for the fast response. Then there is a bug in documentation: http://www.boost.org/doc/libs/1_50_0/doc/html/chrono/users_guide.html Building an Executable that Uses Boost.Chrono<http://www.boost.org/doc/libs/1_50_0/doc/html/chrono/users_guide.html#chrono.users_guide.getting_started.install.building_an_executable_that_uses_boost_chrono_> In addition to link with the *Boost.Chrono* library you need also to link with the *Boost.System* library. Once *Boost.System* will be configurable to be a header only using BOOST_SYSTEM_INLINED you will no need to link with it. Thanks, Dmitriy. On 6 July 2012 00:56, Vicente J. Botet Escriba <vicente.botet@wanadoo.fr>wrote:
Le 05/07/12 19:20, Dmitriy Matison a écrit :
Hi,
On RHEL 5.5 Boost.Chrono 1.1.0 (Boost 1.47.0) fails to run in header only mode with header only Boost.System.
This file can't be compiled:
#define BOOST_SYSTEM_NO_DEPRECATED // without it also error, but in [Boost.System] #define BOOST_SYSTEM_INLINED #define BOOST_CHRONO_HEADER_ONLY
#include <boost/chrono.hpp>
int main() { boost::chrono::steady_clock::**time_point start = boost::chrono::steady_clock::**now(); return 0; }
Error: In function `boost::chrono::steady_clock::**now()': boost/chrono/detail/inlined/**posix/chrono.hpp:85: undefined reference to `boost::system::system_**category()'
Any comments from Chrono\System guys?
Hi,
unfortunately the patch proposed to make Boost.System header only was not accepted.
So even if Boost.Chrono is header-only it depends on a library that is not :(
Best, Vicente ______________________________**_________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/**mailman/listinfo.cgi/boost-**users<http://lists.boost.org/mailman/listinfo.cgi/boost-users>