I am working on a Python package with C++ extensions which have Intel MKL dependency. The extension module links to libmkl_rt.so. I have put mkl>=2019 in the requirements in setup.py.

The MKL itself is a manylinux1 package in the PyPI:
https://pypi.org/project/mkl/#files

However, if I run auditwheel repair to produce a wheel file with manylinux2014 tag. It will copy the libmkl_rt.so into the wheel file. This is of course not needed (and also not preferred). The requirement on MKL is already specified and can be found in the PyPI library. And the auditwheel repair only copies the libmkl_rt.so which is merely an entry for the real MKL library.

Is it a intended behavior of auditwheel repair to copy all the external dynamic dependencies into the wheel file, even if the dependency is a manylinux1 package in the PyPI and the requirements are specified in setup.py? If yes, how I can avoid that the libmkl_rt.so when producing a manylinux2014 wheel?