Boost C++ Libraries: Ticket #12389: Timer expires immediately on Ubuntu 64-bit using boost 1.61

viboes — Mon, 15 Aug 2016 17:18:43 GMT

How is it that you have BOOST_THREAD_HAS_CONDATTR_SET_CLOCK_MONOTONIC some times defined and others not?

Could you elaborate how #11562 is related?

owner, status changed

viboes — Mon, 15 Aug 2016 17:35:15 GMT

owner changed from Anthony Williams to viboes
status new → assigned

anonymous — Tue, 16 Aug 2016 06:32:17 GMT

Our library needs the definition BOOST_THREAD_HAS_CONDATTR_SET_CLOCK_MONOTONIC, to assure system time changes do not affect timer timeout time - ticket #11562 was mentioned only, so you can check how our timers are implemented.

Other libraries that are linked to same application, were not written by us - they work ok without the definition BOOST_THREAD_HAS_CONDATTR_SET_CLOCK_MONOTONIC, a test build with this defition however failed in runtime.

General question is - is it required to have the same definition in all libraries used in application? If so, this is sometimes hard to achieve - e.g.: when you have libraries from different vendors linked together.

viboes — Fri, 19 Aug 2016 21:31:23 GMT

Yes, is it required. BOOST_THREAD_HAS_CONDATTR_SET_CLOCK_MONOTONIC is something that is deduced from the underlying system. Either the system has them or it hasn't. BOOST_THREAD_HAS_CONDATTR_SET_CLOCK_MONOTONIC can be defined by the user only as a workaround to fix an issue on the Boost library.

We could as well issue an error if the user defines it.

status changed; resolution set

viboes — Fri, 19 Aug 2016 22:04:00 GMT

status assigned → closed
resolution → worksforme