[Boost-build] bjam errors during boost compilation with --toolset=intel

Subject: [Boost-build] bjam errors during boost compilation with --toolset=intel
From: Patryk Bukowinski (p.bukowinski_at_[hidden])
Date: 2009-09-22 09:24:08

Hello,
This is my first mail to boost community so please be relatively tolerant ;)

I'm trying to compile latest boost library (currently `1_40_0`) with:
intel compiler (v 11.1).
Microsoft Platform SDK windows XP 32-bit RETAIL
OS - win32 XP

I'm following the instructions on intel site:

http://software.intel.com/en-us/articles/building-boost-with-intel-c/

But the bjam produce me following error:

C:\Documents and Settings\user\Desktop\boost_1_40_0>bjam
>     --toolset="intel" "-sINTEL_PATH=C:\Program
> Files\Intel\Compiler\11.1\038\cpp\ bin\ia32"
> "-sINTEL_BASE_MSVC_TOOLSET=vc-9_0" "-sINTEL_VERSION=11"
>
>     stage 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.
>     warning: Graph library does not contain optional GraphML reader. note:
> to enable GraphML support, set EXPAT_INCLUDE and EXPAT_LIBPATH to the note:
> directories containing the Expat headers and libraries, respectively.
>     warning: Graph library does not contain MPI-based parallel components.
> note: to enable them, add "using mpi ;" to your user-config.jam
>
>     Error: ambiguity found when searching for best transformation Trying to
> produce type 'RC' from:
>      -  { simple_event_log.mc.MC } Generators that succeeded:
>      -  mc.compile
>      -  intel-win.compile.mc First generator produced:
>      -  { mc%mc.compile-simple_event_log.h.H { simple_event_log.mc.MC } }
>      -  { mc%mc.compile-simple_event_log.rc.RC { simple_event_log.mc.MC }
> } Second generator produced:
>      -  { intel-win%intel-win.compile.mc-simple_event_log.h.H {
> simple_event_log.mc. MC } }
>      -  { intel-win%intel-win.compile.mc-simple_event_log.rc.RC {
> simple_event_log.m c.MC } }
>

Compilation with MS CL toolset ends successfully. I haven't found reliable
information about this ambiguity issue.