This page is for supplementary information relating to the implementation described in Section 2.1 of the Installer's Note. It may be augmented over the life-time of the product if further pertinent information becomes available.
This implementation is considered suitable for operation on the computer systems detailed below:
hardware: Intel(R) Mac 64 systems and compatible operating system: Mac OS X 10.10.1 Darwin Kernel Version 14.0.0 and compatible C compiler: Intel(R) C Intel(R) 64 Version 15.0.3.187 and compatible
This implementation has been successfully tested using the following:
hardware: Mac mini 7,1 - 2.6 GHz Intel Core i5 operating system: Mac OS X 10.10.1 Darwin Kernel Version 14.0.0 C compiler: Intel(R) C Intel(R) 64 Compiler XE for applications running on Intel(R) 64, Version 15.0.3.187 Build 20150408 C compiler: Intel(R) C Intel(R) 64 Compiler XE for applications running on Intel(R) 64, Version 16.0.0.083 Build 20150803 C compiler: Apple LLVM version 6.0 (clang-600.0.54) (based on LLVM 3.5svn) hardware: Mac mini 7,1 - 1.4 GHz Intel Core i5 operating system: Mac OS X 10.11.1 Darwin Kernel Version 15.0.0 C compiler: Intel(R) C Intel(R) 64 Compiler XE for applications running on Intel(R) 64, Version 16.0.1.111 Build 20151020 C compiler: Apple LLVM version 7.0.0 (clang-700.1.76) hardware: Mac mini 2.3 GHz Intel Core i5 operating system: Mac OS X 10.8.5 Darwin Kernel Version 12.6.0 C compiler: Intel(R) C Intel(R) 64 Compiler XE Version 14.0.3.166 Build 20140415 hardware: Intel(R) Core(TM) i5-2415M CPU @ 2.30GHz operating system: Mac OS X 10.12.1 C compiler: Intel(R) C Intel(R) 64 Compiler for Intel(R) 64 Version 17.0.1.126 Build 20161013
Please note that when compiling the static MKL-based library libnagc_mkl.a, the link to the runtime library libiomp5.a (version 2015.3.187), supplied with this distribution, will generate warning messages of the form:
ld: warning: can't find atom for N_GSYM stabs ... libiomp5.a(iomp.o)but they do not affect the compilation and execution of the programs with the Library.
This issue appears to have been dealt with if linked to newer versions, such as 2016, of libiomp5.a.