Re: [Boost-users] [chrono] Issues with _ITERATOR_DEBUG_LEVEL

Subject: Re: [Boost-users] [chrono] Issues with _ITERATOR_DEBUG_LEVEL
From: Christian Henning (chhenning_at_[hidden])
Date: 2012-08-10 17:08:57

Here the answer:

On Thu, Aug 9, 2012 at 10:15 PM, Christian Henning <chhenning_at_[hidden]> wrote:
> Hi there, compiling with the latest trunk version gives me the
> following linker error with the chrono lib:
>
> libboost_chrono-vc100-mt-1_51.lib(chrono.obj) : error LNK2038:
> mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match
> value '2' in Factory.obj
>
> Usually the solution is to recompile the lib with
> _ITERATOR_DEBUG_LEVEL=2 but the problem preservers. Can someone tell
> what wrong with compiling boost with:
>
> bjam -j8 --toolset=msvc --without-mpi variant=debug link=static
> runtime-link=shared define=_CRT_NONSTDC_NO_DEPRECATE
> define=_CRT_SECURE_NO_DEPRECATE define=_SCL_SECURE_NO_DEPRECATE
> define="_ITERATOR_DEBUG_LEVEL=2" stage
>
> I mean, is the define="_ITERATOR_DEBUG_LEVEL=2" syntactically correct?

This is correct ( using the " ). The dumpbin tool can be used to
verify that _ITERATOR_DEBUG_LEVEL is set to 2.

Christian