Re: [boost] [program_options + test] Intel problem

From: Bronek Kozicki (brok_at_[hidden])
Date: 2004-08-26 10:01:45

Roland wrote:
> On Thu, 26 Aug 2004 14:34:30 +0400 Vladimir Prus <ghost_at_[hidden]> wrote:
>>Bronek Kozicki says he has tracked down the problem for me: adding
>>"<threading>multi" to boost_thread_lib_base and boost_thread_dll_base
>>in libs\boost\thread\build\jamfile fixes the problem. 
> 
> To be honest, I know not enough about bjam, but perhaps you could
> ask Bronek Kozicki?

I do not know bjam neither, just playing a little with 
libs\thread\test\Jamfile seemed to fix problem with Boost.Threads tests.

However looking at the  http://tinyurl.com/6ynh9 I can see something 
similar to problem with Boost.Threads (besides list of familiar error 
messages). Take a look at list of arguments passed to xilink :
/LIBPATH:"...\program_options\build\libboost_program_options.lib\intel-win32-8.0\debug\runtime-link-static\threading-multi" 

/LIBPATH:"...\test\build\libboost_test_exec_monitor.lib\intel-win32-8.0\debug\runtime-link-static" 

Apparently "libboost_test_exec_monitor.lib" being linked is 
singlethreaded, while "libboost_program_options.lib" is multithreaded. 
This reasults in two different versions of static CRT being brought into 
single excutable, thus error.

Sincerly, when looking at boost\libs\program_options\test\Jamfile I have 
no idea how to update it (as I do not know bjam), and I do not have 
Intel compiler to play with it. If anyone knows bjam well enough and/or 
has Intel compiler, I would suggest seeking for a way to force linking 
with multithreaded version of libboost_test_exec_monitor.lib, instead of 
singlethreaded one.

B.