Link Copied
> Okay, so compiling works, but linking doesn't. What > is the output if you run with -d2 --debug-configuration > I'm guessing that the linker isn't found and ends up > empty, so /lib is interpreted as the program to execute > instead of an argument to the linker. The icl.exe tool isn't being found but I have no idea why. Here was the result of running with the debug config: \boost_1_48_0>bjam --toolset="intel" "-sINTEL_PATH=C :\Program Files (x86)\Intel\Composer XE\bin\ia32" "-sINTEL_BASE_MSVC_TOOLSET=vc -10_0" "-sINTEL_VERSION=12.1" -2 --debug-configuration notice: found boost-build.jam at C:/Users/Kim/Desktop/boost_1_48_0/boost -build.jam notice: loading Boost.Build from C:/Users/Kim/Desktop/boost_1_48_0/tools /build/v2 notice: [msvc-cfg] msvc-10.0 detected, command: 'C:\Program Files (x86)\Microsof t Visual Studio 10.0\VC\bin\cl.exe' notice: [msvc-cfg] msvc-9.0 detected, command: 'C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\bin\cl.exe' notice: will use 'C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\cl. exe' for msvc, conditionmsvc-10.0 notice: [msvc-cfg] condition: ' msvc-10.0/ / ', setup: 'call "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\vcvarsal l.bat" x86 >nul ' notice: [msvc-cfg] condition: ' msvc-10.0/ / 32', setup: 'call "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\vcvars all.bat" x86 >nul ' notice: [msvc-cfg] condition: ' msvc-10.0/ x86/ ', setup: 'call "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\vcvar sall.bat" x86 >nul ' notice: [msvc-cfg] condition: ' msvc-10.0/ x86/ 32', setup: 'call "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\vcv arsall.bat" x86 >nul ' notice: [msvc-cfg] condition: ' msvc-10.0/ / 64', setup: 'call "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\vcvars all.bat" x86_amd64 >nul ' notice: [msvc-cfg] condition: ' msvc-10.0/ x86/ 64', setup: 'call "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\vcv arsall.bat" x86_amd64 >nul ' notice: [msvc-cfg] condition: ' msvc-10.0/ ia64/ ', setup: 'call "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\vcva rsall.bat" x86_ia64 >nul ' notice: [msvc-cfg] condition: ' msvc-10.0/ ia64/ 64', setup: 'call "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\vc varsall.bat" x86_ia64 >nul ' warning: toolset intel-win initialization: can not find tool icl.exe warning: initialized from notice: will use 'icl.exe' for intel-win, condition intel-win notice: iostreams: not using zlib compression notice: iostreams: not using zlib compression notice: iostreams: not using bzip2 compression notice: iostreams: not using bzip2 compression Building the Boost C++ Libraries. At which point it started bringing up the can't open file windows.
In boost\tools\build\v2\user-config.jam I modified the using statement to:
using intel-win : 12.1 : "C:/Program Files (x86)/Intel/Composer XE 2011 SP1/bin/ia32/icl.exe" ;
----
I didn't do that. I tried changing the .jam to see if it would start giving me an error, but it didn't.
I think what I'd like to know is if before you start running b2, if you can just run "icl" and actually run the compiler, or if you get the "icl.exe not recognized" problem you see from your build log.
For more complete information about compiler optimizations, see our Optimization Notice.