OMP: Error #15: Initializing libomp.dylib, but found libiomp5.dylib already initialized.
OMP: Hint: This means that multiple copies of the OpenMP runtime have been linked into the program. That is dangerous, since it can degrade performance or cause incorrect results. The best thing to do is to ensure that only a single OpenMP runtime is linked into the process, e.g. by avoiding static linking of the OpenMP runtime in any library. As an unsafe, unsupported, undocumented workaround you can set the environment variable KMP_DUPLICATE_LIB_OK=TRUE to allow the program to continue to execute, but that may cause crashes or silently produce incorrect results. For more information, please see http://www.intel.com/software/products/support/.
- OMP: Erro
“OMP: Error #15: Initializing libguide.dylib, but found libiomp5.dylib already initialized” is a linker error generated when different parts of a program try to link both static and dynamic verions of the OpenMP runtime. The solution is to explicitly call out either a dynamic or static link. The Intel compiler options for specifying the OpenMP library to be linked on Mac OS X* is -openmp-link static and -openmp-link dynamic.
This error has also been reported when two or more versions of MKL were installed. Under this scenario, some files were being linked from one MKL version and some were being linked from another MKL version. Setting the dynamic library enviornment variable DYLD_LIBRARY_PATH to include a path to only one MKL version resolved this issue.
-
LD_LIBRARY_PATH环境变量的设置
https://blog.csdn.net/mmyaoduli/article/details/49798333 -
Linux环境变量LD_LIBRARY_PATH
https://blog.csdn.net/huangyimo/article/details/80580442 -
Mac OS DYLD_LIBRARY_PATH 环境变量说明
https://blog.csdn.net/starshine/article/details/69525459 -
Using the OpenMP* Libraries
https://software.intel.com/en-us/node/522690 -
qopenmp-link
https://software.intel.com/en-us/node/678116?language=ru