Hi, thanks for feedback.

This is certainly close.

Now I've different error messages, but no more ambiguity problem (quote text).

I've solved all issues with following:

In Jamfile for this lib, there is a section that is dependent on Message Compiler.
I've commented it out and created headers by my own.
Then the whole build run without errors.



After adding Your adjustments to intel-win.jam:

generators.override intel-win.compile.mc : mc.compile ;

I have:

lib.jam: No such file or directory
warning: Building Boost.Regex with the optional Unicode/ICU support disabled.
note: Please refer to the Boost.Regex documentation for more information
note: this is a strictly optional feature.
...patience...
...patience...
...found 2258 targets...
...updating 6 targets...
intel-win.compile.mc ..\..\..\bin.v2\libs\log\build\intel-win\debug\threading-multi\simple_event_log.h
'-h' is not recognized as an internal or external command,
operable program or batch file.

      -h "..\..\..\bin.v2\libs\log\build\intel-win\debug\threading-multi" -r "..\..\..\bin.v2\libs\log\build\intel-win\d
ebug\threading-multi" "..\..\..\libs\log\src\simple_event_log.mc"

...failed intel-win.compile.mc ..\..\..\bin.v2\libs\log\build\intel-win\debug\threading-multi\simple_event_log.h ..\..\.
.\bin.v2\libs\log\build\intel-win\debug\threading-multi\simple_event_log.rc...
...skipped <p..\..\..\bin.v2\libs\log\build\intel-win\debug\threading-multi>simple_event_log_res.obj for lack of <p..\..
\..\bin.v2\libs\log\build\intel-win\debug\threading-multi-object(res-scanner)@935>simple_event_log.rc...
...skipped <p..\..\..\bin.v2\libs\log\build\intel-win\debug\threading-multi>boost_log-iw-mt-gd-1_40.dll for lack of <p..
\..\..\bin.v2\libs\log\build\intel-win\debug\threading-multi>simple_event_log_res.obj...
...skipped <p..\..\..\bin.v2\libs\log\build\intel-win\debug\threading-multi>boost_log-iw-mt-gd-1_40.lib for lack of <p..
\..\..\bin.v2\libs\log\build\intel-win\debug\threading-multi>simple_event_log_res.obj...
...skipped <p..\..\..\bin.v2\libs\log\build\intel-win\debug\threading-multi>boost_log-iw-mt-gd-1_40.pdb for lack of <p..
\..\..\bin.v2\libs\log\build\intel-win\debug\threading-multi>simple_event_log_res.obj...
...failed updating 2 targets...
...skipped 4 targets...


I can assume that the problem for me is partially solved, but If You have some ideas how to solve those MC issues, I can test it on my side.

thanks for help.


2009/9/23 Vladimir Prus <vladimir@codesourcery.com>
Patryk Bukowinski wrote:

> I've found that the problem is caused by third party library, boost-log from
> boost.pro.
> With this library deleted from boost dir tree, everything compile correctly
> with intel-toolset.
> I just wanted to compile boost with that library, could You help me adjust
> the jamfile to use intel properly.
> File in attachment.

Patryk,

if you use third-party library, this explains the error. Can you try to
apply the attached patch to tools/build/v2/tools/intel-win.jam and
try again?

The Jamfile for the library has an unrelated issue, but I assume you're not
maintainer of it so it should not matter.

- Volodya


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