Opened 10 years ago
Last modified 8 years ago
#8235 new Bugs
Toolset “intel-win” fails on .asm files
| Reported by: | Owned by: | Vladimir Prus | |
|---|---|---|---|
| Milestone: | To Be Determined | Component: | build |
| Version: | Boost 1.53.0 | Severity: | Problem |
| Keywords: | assembler | Cc: |
Description
Building boost v1.53.0 using intel-win fails because assembler (masm or ml/ml64) doesn’t set:
intel-win.compile.asm bin.v2\libs\context\build\intel-win\debug\link-static\threading-multi\asm\make_x86_64_ms_pe_masm.obj '-c' is not recognized as an internal or external command, operable program or batch file.
-c -Zp4 -Cp -Cx -DBOOST_ALL_NO_LIB=1 -DBOOST_ALL_NO_LIB=1 /Zi /Zd /W3 -Fo "bin.v2\libs\context\build\intel-win\debug\link-static\threadingmulti\asm\make_x86_64_ms_pe_masm.obj" "libs\context\src\asm\make_x86_64_ms_pe_masm.asm"
...failed intel-win.compile.asm bin.v2\libs\context\build\intel-win\debug\link-static\threading-multi\asm\make_x86_64_ms_pe_masm.obj... intel-win.compile.asm bin.v2\libs\context\build\intel-win\debug\link-static\threading-multi\asm\jump_x86_64_ms_pe_masm.obj '-c' is not recognized as an internal or external command, operable program or batch file.
Adding to tools/build/v2/tools/intel-win.jam a line toolset.flags intel-win.compile .ASM $(condition) : ml64 ( for icl Intel64) or
toolset.flags intel-win.compile .ASM $(condition) : ml64 (for icl IA32) resolves this problem.
This problem is discussed also on http://software.intel.com/en-us/forums/topic/494996 and updated intel-win.jam is attached for fix this problem.