使用openmp时，xtensor-python-cookiecutter无法成功构建我的模块

如何解决使用openmp时，xtensor-python-cookiecutter无法成功构建我的模块

在xtensor-python-cookiecutter中的xtensor-python中使用openmp时遇到问题。

执行import numpy as np A = np.array([[1,1,0],[1,1],[0,1]]) B = np.array([0,1]) X = np.linalg.inv(A).dot(B) print(X) 后，在python setup.py build：import myLib时遇到错误。

下面是我的undefined symbol: omp_get_thread_num

日志

python setup.py build

检查最后一条命令：

$ py setup.py build
running build
running build_ext
creating tmp
gcc -pthread -B /home/joker/.miniconda3/envs/cpp/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/home/joker/.miniconda3/envs/cpp/include/python3.8 -c /tmp/tmp8bct6mhu.cpp -o tmp/tmp8bct6mhu.o -std=c++14
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++
gcc -pthread -B /home/joker/.miniconda3/envs/cpp/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/home/joker/.miniconda3/envs/cpp/include/python3.8 -c /tmp/tmpja5ljvir.cpp -o tmp/tmpja5ljvir.o -fvisibility=hidden
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++
building 'test' extension
creating build
creating build/temp.linux-x86_64-3.8
creating build/temp.linux-x86_64-3.8/src
gcc -pthread -B /home/joker/.miniconda3/envs/cpp/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/home/joker/.miniconda3/envs/cpp/include -I/home/joker/.miniconda3/envs/cpp/include -I/home/joker/.miniconda3/envs/cpp/lib/python3.8/site-packages/numpy/core/include -I/home/joker/.miniconda3/envs/cpp/include -I/home/joker/.miniconda3/envs/cpp/Library/include -I/home/joker/.miniconda3/envs/cpp/include/python3.8 -c src/main.cpp -o build/temp.linux-x86_64-3.8/src/main.o -fopenmp -DVERSION_INFO="0.1.0" -std=c++14 -fvisibility=hidden
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++
creating build/lib.linux-x86_64-3.8
g++ -pthread -shared -B /home/joker/.miniconda3/envs/cpp/compiler_compat -L/home/joker/.miniconda3/envs/cpp/lib -Wl,-rpath=/home/joker/.miniconda3/envs/cpp/lib -Wl,--no-as-needed -Wl,--sysroot=/ build/temp.linux-x86_64-3.8/src/main.o -o build/lib.linux-x86_64-3.8/test.cpython-38-x86_64-linux-gnu.so

似乎缺少g++ -pthread -shared -B /home/joker/.miniconda3/envs/cpp/compiler_compat -L/home/joker/.miniconda3/envs/cpp/lib -Wl,--sysroot=/ build/temp.linux-x86_64-3.8/src/main.o -o build/lib.linux-x86_64-3.8/test.cpython-38-x86_64-linux-gnu.so 。用-fopenmp（即

）手动运行后

-fopenmp

一切都很好。

我在g++ -fopenmp -pthread -shared -B /home/joker/.miniconda3/envs/cpp/compiler_compat -L/home/joker/.miniconda3/envs/cpp/lib -Wl,--sysroot=/ build/temp.linux-x86_64-3.8/src/main.o -o build/lib.linux-x86_64-3.8/test.cpython-38-x86_64-linux-gnu.so 中添加了标志 -fopenmp ，但是我不知道为什么它不能按预期运行

setup.py

感谢您的阅读。

下面是我的完整class BuildExt(build_ext): """A custom build extension for adding compiler-specific options.""" c_opts = { 'msvc': ['/EHsc'],'unix': ['-fopenmp'],}

setup.py

再次感谢。