Archlinux: Slycot compiled against MKL crashes #138
Labels
build system
Issues with compiling, linking and installing Slycot
Comments
|
Hi, I doubt that it is the specific test. Try running with The error message looks like your MKL installation is incomplete. |
acxz
changed the title
|
If you search for I also just tried to build slycot on Archlinux with intel-mkl installed:
|
hmm weird that doesn't seem to be happening for me. I think for now I'll stick with the pip package instead of using the AUR package. |
And that one finds and builds against MKL fine? Can you post the buildlog? |
|
Note that the AUR package is the PyPI source package plus a recipe how to build it for the Archlinux system. We do not provide wheels. If you need it precompiled, use conda. Alternatovely you can try https://build.opensuse.org/package/show/home:bnavigator:archlinux/python-slycot. In that repo, I am also preparing a |
bnavigator
added
the
build system
For the pip package I am not building it just using In any case I am more interested in getting the AUR package working with the build log here: AUR build log |
|
pip is building your slycot wheel from source. Please use |
|
|
|
You have to clear your pip cache first |
|
Now there is also an arch package built against MKL from I installed it on my Archlinux machine together with |
bnavigator
changed the title
ah my bad I have updated the gist: https://gist.github.com/acxz/9f52adbc843bb4d6da538ffa5a518cf9
Sweet! I prob won't use it unless its on the AUR tho.. |
|
That log is still garbage. Have you even tried to look into it? I can only reiterate what is written all over the Arch wiki: If you don't know how to build your own package from a PKGBUILD, you should not use AUR either. Anyway here is the AUR package: https://aur.archlinux.org/packages/python-slycot-mkl/ |
Ah once again sorry about that. I should have been more specific. The relevant content is near the bottom. You need to view the entire file not just the preview on gist. Here is the link for easy access. https://gist.githubusercontent.com/acxz/9f52adbc843bb4d6da538ffa5a518cf9/raw/a13e11997576cd2221a4ecaf49138d1bbfe15c9b/slycot-pip-install-no-cache.txt Thx for creating the AUR package, |
|
Hmm, now I see that you are the maintainer of >500 packages in AUR. Honestly, I am surprised you are not able to provide the relevant information right away, not to mention the misuse of the out-of-date flag. So your pip build finds the same MKL as your yay/AUR build. It does not run the unit tests. But does the pip package actually work? What does |
|
|
|
A crash. Pip package won't help you then. |
Okay, now my default package also finds MKL. Maybe the environment was not reloaded on my first tries. If you compile against a specific BLAS/LAPACK implementation, your whole ecosystem including numpy and scipy need to be linked to the same implementation. This is highly distribution specific. When mixing package repositories (conda, pip wheels, official distribution, additional repositories like AUR, custom PPAs, ...) chances are high that the packages are incompatible because they link to different implementations. OTOH, if you link against an installed reference NetLIB BLAS/LAPACK implementation ( I could not find any guidelines for Archlinux packaging. The python-numpy packages has Tl;dr: Link all your libraries against the same LAPACK/BLAS implementation. For your specific case, you have several options:
|
|
Closing, as we cannot do anything about this "upstream". If anyone thinks otherwise, please comment or open a new issue/PR with your proposal. |
|
thx for getting down to the bottom of this @bnavigator ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When running the test suite,
test_ab01.pyfails for me with the following error:Specifically:
If I compile and run the test_suite without intel-mkl on my system the test_suite runs successfully.
System:
Version: 0.4.0
OS: ArchLinux
Intel-MKL: 2020.2.254
Python: 3.8.5
Let me know if I can give more information.
The text was updated successfully, but these errors were encountered: