报错:OMP: Error #15: Initializing libomp.dylib, but found libiomp5.dylib already initialized.
問題描述:
OMP: Error #15: Initializing libiomp5.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/.解決方案:
import os os.environ["KMP_DUPLICATE_LIB_OK"]="TRUE"If you are using Python distributed by Conda, then it is highly likely that the error is caused by the numpy package from Conda which includes the mkl package which in turn conflicts with the system-wide library. In this case you can update the numpy package in Conda or replace the Conda’s OpenMP library instance with system-wide one by creating a symlink to it in Conda environment folder $CONDA_PREFIX/lib.
如果Python是基本于Conda安裝的,則Conda上的numpy包中的mkl很容易與系統內庫發生沖突,可選擇update numpy package in Conda或者設置為系統庫。
通過降低matplotlib的版本,即conda install matplotlib=2.2.3來解除阻塞
總結
以上是生活随笔為你收集整理的报错:OMP: Error #15: Initializing libomp.dylib, but found libiomp5.dylib already initialized.的全部內容,希望文章能夠幫你解決所遇到的問題。
- 上一篇: 数据结构之并查集:并查集解决案例, Py
- 下一篇: recover 没有捕获异常_defer