Compilation errors building boost with intel compiler

[Charles_G_]

Intel compiler version: 16.0

Boost version: 1.60

Mac running 10.11 (El Capitan) on a Macbook Pro with an Intel Core i7 (2011)

I followed the instructions here very closely: https://software.intel.com/en-us/articles/building-boost-with-intel-c-compiler-150 and I get errors like these:

Jamfile</Users/cgreen/software/boost_1_60_0/libs/context/build>.gas64 ../boost_build/boost/bin.v2/libs/context/build/intel-darwin-16.0/release/threading-multi/asm/make_x86_64_sysv_macho_gas.o
clang: error: unsupported option '--64'
clang: error: no input files

    cpp -x assembler-with-cpp "libs/context/src/asm/make_x86_64_sysv_macho_gas.S" | as --64 -o "../boost_build/boost/bin.v2/libs/context/build/intel-darwin-16.0/release/threading-multi/asm/make_x86_64_sysv_macho_gas.o"

...failed Jamfile</Users/cgreen/software/boost_1_60_0/libs/context/build>.gas64 ../boost_build/boost/bin.v2/libs/context/build/intel-darwin-16.0/release/threading-multi/asm/make_x86_64_sysv_macho_gas.o...
Jamfile</Users/cgreen/software/boost_1_60_0/libs/context/build>.gas64 ../boost_build/boost/bin.v2/libs/context/build/intel-darwin-16.0/release/threading-multi/asm/jump_x86_64_sysv_macho_gas.o
clang: error: unsupported option '--64'
clang: error: no input files

    cpp -x assembler-with-cpp "libs/context/src/asm/jump_x86_64_sysv_macho_gas.S" | as --64 -o "../boost_build/boost/bin.v2/libs/context/build/intel-darwin-16.0/release/threading-multi/asm/jump_x86_64_sysv_macho_gas.o"

...failed Jamfile</Users/cgreen/software/boost_1_60_0/libs/context/build>.gas64 ../boost_build/boost/bin.v2/libs/context/build/intel-darwin-16.0/release/threading-multi/asm/jump_x86_64_sysv_macho_gas.o...
common.mkdir ../boost_build/boost/bin.v2/libs/context/build/intel-darwin-16.0/release/threading-multi/posix

And later more errors:

intel-darwin.link.dll ../boost_build/boost/bin.v2/libs/locale/build/intel-darwin-16.0/release/threading-multi/libboost_locale.dylib
Undefined symbols for architecture x86_64:
  "__ZNSt3__110moneypunctIcLb0EED2Ev", referenced from:
      __ZN5boost6locale8impl_std17create_formattingERKNSt3__16localeERKNS2_12basic_stringIcNS2_11char_traitsIcEENS2_9allocatorIcEEEEjNS1_12utf8_supportE in numeric.o
      __ZN5boost6locale8impl_std14create_parsingERKNSt3__16localeERKNS2_12basic_stringIcNS2_11char_traitsIcEENS2_9allocatorIcEEEEjNS1_12utf8_supportE in numeric.o
      __ZN5boost6locale8impl_std25utf8_moneypunct_from_wideILb0EED1Ev in numeric.o
      __ZN5boost6locale8impl_std25utf8_moneypunct_from_wideILb0EED0Ev in numeric.o
      __ZN5boost6locale8impl_std15utf8_moneypunctILb0EED1Ev in numeric.o
      __ZN5boost6locale8impl_std15utf8_moneypunctILb0EED0Ev in numeric.o
      __ZN5boost6locale8impl_std20create_basic_parsingIcEENSt3__16localeERKS4_RKNS3_12basic_stringIcNS3_11char_traitsIcEENS3_9allocatorIcEEEE in numeric.o
      ...
  "__ZNSt3__110moneypunctIcLb1EED2Ev", referenced from:
      __ZN5boost6locale8impl_std17create_formattingERKNSt3__16localeERKNS2_12basic_stringIcNS2_11char_traitsIcEENS2_9allocatorIcEEEEjNS1_12utf8_supportE in numeric.o
      __ZN5boost6locale8impl_std14create_parsingERKNSt3__16localeERKNS2_12basic_stringIcNS2_11char_traitsIcEENS2_9allocatorIcEEEEjNS1_12utf8_supportE in numeric.o
      __ZN5boost6locale8impl_std25utf8_moneypunct_from_wideILb1EED1Ev in numeric.o
      __ZN5boost6locale8impl_std25utf8_moneypunct_from_wideILb1EED0Ev in numeric.o
      __ZN5boost6locale8impl_std15utf8_moneypunctILb1EED1Ev in numeric.o
      __ZN5boost6locale8impl_std15utf8_moneypunctILb1EED0Ev in numeric.o
      __ZN5boost6locale8impl_std20create_basic_parsingIcEENSt3__16localeERKS4_RKNS3_12basic_stringIcNS3_11char_traitsIcEENS3_9allocatorIcEEEE in numeric.o
      ...
  "__ZNSt3__110moneypunctIwLb0EED2Ev", referenced from:
      __ZN5boost6locale8impl_std14create_parsingERKNSt3__16localeERKNS2_12basic_stringIcNS2_11char_traitsIcEENS2_9allocatorIcEEEEjNS1_12utf8_supportE in numeric.o
      __ZN5boost6locale8impl_std20create_basic_parsingIwEENSt3__16localeERKS4_RKNS3_12basic_stringIcNS3_11char_traitsIcEENS3_9allocatorIcEEEE in numeric.o
  "__ZNSt3__110moneypunctIwLb1EED2Ev", referenced from:
      __ZN5boost6locale8impl_std14create_parsingERKNSt3__16localeERKNS2_12basic_stringIcNS2_11char_traitsIcEENS2_9allocatorIcEEEEjNS1_12utf8_supportE in numeric.o
      __ZN5boost6locale8impl_std20create_basic_parsingIwEENSt3__16localeERKS4_RKNS3_12basic_stringIcNS3_11char_traitsIcEENS3_9allocatorIcEEEE in numeric.o
  "__ZNSt3__18time_putIcNS_19ostreambuf_iteratorIcNS_11char_traitsIcEEEEED2Ev", referenced from:
      __ZN5boost6locale10impl_posix14time_put_posixIcED1Ev in numeric.o
      __ZN5boost6locale10impl_posix14time_put_posixIcED0Ev in numeric.o
      __ZN5boost6locale8impl_std23utf8_time_put_from_wideD1Ev in numeric.o
      __ZN5boost6locale8impl_std23utf8_time_put_from_wideD0Ev in numeric.o
      __ZN5boost6locale8impl_std18time_put_from_baseIcED1Ev in numeric.o
      __ZN5boost6locale8impl_std18time_put_from_baseIcED0Ev in numeric.o
  "__ZNSt3__18time_putIwNS_19ostreambuf_iteratorIwNS_11char_traitsIwEEEEED2Ev", referenced from:
      __ZN5boost6locale10impl_posix14time_put_posixIwED1Ev in numeric.o
      __ZN5boost6locale10impl_posix14time_put_posixIwED0Ev in numeric.o
      __ZN5boost6locale8impl_std18time_put_from_baseIwED1Ev in numeric.o
      __ZN5boost6locale8impl_std18time_put_from_baseIwED0Ev in numeric.o
ld: symbol(s) not found for architecture x86_64

Any ideas?

[Kittur_G_Intel]

Hi Charles,
Just letting you know I'll investigate this and see if I can reproduce the issue so I  can file the issue with the developers. I'll keep you updated right after. Appreciate your patience till then

Kittur

[Charles_G_]

Kittur Ganesh (Intel) wrote:

Just letting you know I'll investigate this and see if I can reproduce the issue so I  can file the issue with the developers. I'll keep you updated right after. Appreciate your patience till then

Kittur

Thanks! I would be fine with using an older version of boost for my application but I get similar errors for boost 1.58 and 1.59 (using the same intel compiler 16.0).

[Kittur_G_Intel]

Thanks Charles, I'll file the issue with the developers and will keep you updated. Appreciate your patience till then.

Regards,
Kittur

[Charles_G_]

Any updates? Were you able to reproduce the problem?

[Kittur_G_Intel]

Hi Charles,
As mentioned I've already filed the issue (# DPD200409904) with the developers and is under investigation from their end. I'll keep you updated and will update you accordingly as and when I get an update from them.  Appreciate your patience till then. BTW, I've also let them know that you did inquire on the status as well, thanks.

Regards,
Kittur

[Kittur_G_Intel]

Hi Charles,
Just letting you know that this issue will be fixed in next update 4 release and I'll keep you updated as soon as the release with the fix is out. Appreciate your patience through this, as always.
Regards,
Kittur 

[Jay_E_]

Is there an approximate timeframe for update 4? I'm having the same problem.

[TimP]

Wasn't it mentioned on the forum that 2016 update 4 should appear next month?

[Kevin_D_Intel]

I don't know if it was but its more like in the September time-frame, and that comes with all the standard caveats, disclaimers, not a promise, etc. There's always a chance something may delay that.

[JenniferJ]

There is an issue in boost and it should be fixed in boost 1.62: https://svn.boost.org/trac/boost/ticket/12242

Please try again with boost 1.62 and latest ICC 16.0 update 3. Let us know if it works.  

Thanks,

Jennifer