2013/1/6 Eric Niebler <eric@boostpro.com>
Can anybody comment on this?
msvc.link.dll bin.v2\libs\context\build\msvc-11.0\debug\threading-multi\boost_context-vc110-mt-gd-1_53.dll Creating library bin.v2\libs\context\build\msvc-11.0\debug\threading-multi\boost_context-vc110-mt-gd-1_53.lib and object bin.v2\libs\context\build\msvc-11.0\ debug\threading-multi\boost_context-vc110-mt-gd-1_53.exp make_i386_ms_pe_masm.obj : error LNK2019: unresolved external symbol __exit referenced in function _make_fcontext LINK : error LNK2001: unresolved external symbol __DllMainCRTStartup@12 I assume the error report refers to target-os=Windows (32bit) As the error describes the linker can not find symbol __exit (note two underscores!). the assembler code in make_i386_ms_pe_masm.asm calls _exit (_exit() from c-library) - I don't know why the assembler (is it MASM?, which version?) adds a leading underscore to _exit (and _DllMainCRTStartup too). If take a I look at the regression tests in trunk I see that the test pass ( teeks99-1a-win7-32on64).<http://www.boost.org/development/tests/trunk/teeks99-1a-win7-32on64.html> Even __DllMainCRTStartup should be _DllMainCRTStartup. maybe some additional compiler flags are responsive for this behaviour?