@carlosal1015

Intel MKL has a symlink, so one can use

export LD_LIBRARY_PATH=/opt/intel/oneapi/mkl/latest/lib:$LD_LIBRARY_PATH

to have a version-independent solution

Important note: After installation, append this line

export LD_LIBRARY_PATH=/opt/intel/oneapi/mkl/2024.1/lib:$LD_LIBRARY_PATH

in ~/.bashrc, ~/.zshrc, etc. In order to avoid this ImportError.

I've encountered the following error with h5py, which is build against the pre 2.0 version of default NumPy from https://archlinux.org/packages/extra/x86_64/python-numpy:

numpy.dtype size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObject

meson-python is 0.16.0 now, which is incompatible with pyproject.toml We can fix it by adding sed -i -e "s/,<0.16.0//g" pyproject.toml to PKGBUILD.

intel-oneapi-mkl is mentioned as dependency but this package does not contain the required opt/intel/oneapi/setvars.sh, which is provided by intel-oneapi-basekit or intel-oneapi-common

Update:

to fix this issue, make sure /opt/intel/oneapi/mkl/latest/lib/intel64 is in LD_LIBRARY_PATH.

I have the issue of loading MKL in a fresh new build.

Python 3.11.5 (main, Sep  2 2023, 14:16:33) [GCC 13.2.1 20230801] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import numpy
Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/numpy/core/__init__.py", line 24, in <module>
    from . import multiarray
  File "/usr/lib/python3.11/site-packages/numpy/core/multiarray.py", line 10, in <module>
    from . import overrides
  File "/usr/lib/python3.11/site-packages/numpy/core/overrides.py", line 8, in <module>
    from numpy.core._multiarray_umath import (
ImportError: libmkl_intel_lp64.so.2: cannot open shared object file: No such file or directory

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/numpy/__init__.py", line 130, in <module>
    from numpy.__config__ import show as show_config
  File "/usr/lib/python3.11/site-packages/numpy/__config__.py", line 4, in <module>
    from numpy.core._multiarray_umath import (
  File "/usr/lib/python3.11/site-packages/numpy/core/__init__.py", line 50, in <module>
    raise ImportError(msg)
ImportError: 

IMPORTANT: PLEASE READ THIS FOR ADVICE ON HOW TO SOLVE THIS ISSUE!

Importing the numpy C-extensions failed. This error can happen for
many reasons, often due to issues with your setup or how NumPy was
installed.

We have compiled some common reasons and troubleshooting tips at:

    https://numpy.org/devdocs/user/troubleshooting-importerror.html

Please note and check the following:

  * The Python version is: Python3.11 from "/usr/bin/python"
  * The NumPy version is: "1.26.0"

and make sure that they are the versions you expect.
Please carefully study the documentation linked above for further help.

Original error was: libmkl_intel_lp64.so.2: cannot open shared object file: No such file or directory


The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python3.11/site-packages/numpy/__init__.py", line 135, in <module>
    raise ImportError(msg) from e
ImportError: Error importing numpy: you should not try to import numpy from
        its source directory; please exit the numpy source tree, and relaunch
        your python interpreter from there.

would it be possible to update the build instructions to those in the regular numpy package? There is a recent update that solves an issue with python-statsmodels and it does not rely on setup.py

I'm not sure if this is the cause to the difference but extra-x86_64-build will call makechrootpkg using configurations under /usr/share/devtools.

@petronny thanks for the response. is there any difference between building with makechrootpkg -c -r $CHROOT and extra-x86_64-build? becase thats the only thing that i am doing differently.