What have happened is :
intel-win.compile.rc boost\bin.v2\libs\log\build\intel-win\debug\threading-multi\simple_event_log_res.obj
'-l' is not recognized as an internal or external command,
operable program or batch file.

     -l 0x409  -DBOOST_ALL_NO_LIB=1 -DBOOST_DATE_TIME_DYN_LINK=1 -DBOOST_FILESYSTEM_DYN_LINK=1 -DBOOST_LOG_BUILDING_THE_
LIB=1 -DBOOST_LOG_DLL -DBOOST_SYSTEM_DYN_LINK=1 -DBOOST_THREAD_USE_DLL=1 -DDATE_TIME_INLINE -I"..\..\.." -I"boost\bin.v2
\libs\log\build\intel-win\debug\threading-multi" -fo "boost\bin.v2\libs\log\build\intel-win\debug\threading-multi\simple
_event_log_res.obj" "boost\bin.v2\libs\log\build\intel-win\debug\threading-multi\simple_event_log.rc"

...failed intel-win.compile.rc boost\bin.v2\libs\log\build\intel-win\debug\threading-multi\simple_event_log_res.obj...
compile-c-c++ boost\bin.v2\libs\log\build\intel-win\debug\threading-multi\code_conversion.obj
icl: command line remark #10010: option '/Op' is deprecated and will be removed in a future release. See '/help deprecat
ed'

So simply the library couldn't be linked.
It was working when I had this *.h file in library src folder (the same where *.mc file was).

Wondering is that an jamfile issue, or still the intel-win.jam, because I remind that for msvc this works.



2009/9/23 Vladimir Prus <ghost@cs.msu.su>
On Wednesday 23 September 2009 Patryk Bukowinski wrote:

> I've removed *.h files which I've generated manually,
> then apply Your new line (to intel-win.jam which is placed in its regular
> directory):
>
> toolset.flags intel-win.link .MC $(condition) : $(setup)mc ;

Oh, sorry, it's too late here already. This should have been:

       toolset.flags intel-win.compile .MC $(condition) : $(setup)mc ;

That is 'compile', not 'link'.

Does that help?

- Volodya
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build