Intel(R) - Computational and Systems Biology at MIT

Linking Your Application with Intel® Math Kernel Library 5Notes on LinkingUpdating LD_LIBRARY_PATHWhen using the Intel MKL shared libraries, do not forget to update the shared librariesenvironment path, that is, a system variable LD_LIBRARY_PATH, to include the librarieslocation. For example, if the Intel MKL libraries are in the/opt/intel/mkl/10.0.xxx/lib/32 directory (where xxx is the Intel MKL packagenumber, for instance, "039"), then the following command line can be used (assuming abash shell):export LD_LIBRARY_PATH=/opt/intel/mkl/10.0.xxx/lib/32:$LD_LIBRARY_PATHLinking with libguideIf you link with libguide statically (discouraged)• and use the Intel® compiler, then link in the libguide version that comes with thecompiler, that is, use -openmp option.• but do not use the Intel compiler, then link in the libguide version that comes withIntel MKL.If you use dynamic linking (libguide.so) of the threading library (recommended), makesure the LD_LIBRARY_PATH is defined so that exactly this version of libguide is foundand used at run time.Building Custom Shared ObjectsCustom shared objects enable reducing the collection of functions available in Intel MKLlibraries to those required to solve your particular problems, which helps to save disk spaceand build your own dynamic libraries for distribution.Intel MKL Custom Shared Object BuilderCustom shared object builder is targeted for creation of a dynamic library (shared object)with selected functions and located in tools/builder directory. The builder contains amakefile and a definition file with the list of functions. The makefile has three targets:"ia32", "ipf", and "em64t". "ia32" target is used for processors using IA-32 architecture,"ipf" is used for IA-64 architecture, and "em64t" is used for Intel® Xeon® processorusing Intel® 64 architecture.5-11