-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ImportError: DLL load failed while importing _scs_direct #47
Comments
It looks to me like this can't find the actual scs dll, rather than the blas dll. Can you try pointing all the PATH variables (PYTHON_PATH etc) to wherever the _scs_direct dll library has been installed? |
I got that error regarding _scs_direct when conda pulled the pypy build of scs in instead of the cpython version which is suitable for my conda installation. Reinstalling scs with the specific build solved the problem for me. The specific cpython build was scs=3.0.0=py37hd9fb7ff_0. |
Hi, I'm helping to package scs for conda-forge. What you describe shouldn't happen, can you explain how you arrived in such a state? |
I don't really know how I arrived in that state. My conda is version 4.10.3 and win64. First, conda couldn't resolve the environment, i.e. conda install .. hanged in "Solving environment /", but this is not an scs issue. I could not install anything anymore. Then I've tried to resolve the issue with some hints in conda/conda#7690 or conda/conda#8051 which didn't really help. After some commenters complaining about memory size during package resolving, I've tried to install scs with mamba. Mamba allowed me to install packages, but somehow pulled in the pypy version of scs. This could be a mamba issue also. |
I am experiencing the same problem when installing scs from source on Windows. I cloned the lastest version of scs-python from git.
The output was
However when importing scs I get the following error
I can see that scs is installed in the following structure
When I check sys.path I get the following output.
So far I have not been able to make it work |
Have you made sure your PATH variables are pointing to the SCS install directory? |
I am not sure what you mean by your question. I am a bit new to installing modules from source. |
Yeah the DLL loader needs to know where the libraries are installed, looks like it's somewhere inside |
I managed to fix the problem. Firstly, I did a re-install of scs where i called There error continued, but I then used Process Monitor as suggested here to check the name of DLLs Python was looking for. Also thank you @bodono for the quick responses. |
I am building scs for Python 3.8 on Windows, and I keep getting this error when trying to import scs.
I linked NumPy to OpenBLAS, so scs should be building with it as well. I'm not sure what DLL it is looking for, but I did put C:/OpenBLAS/bin in my Path variable. I also looked inside the site-packages folder, and there does exist a file named _scs_direct.cp38-win_amd64.pyd, not sure if it's related though.
This is what NumPy outputs currently:
The text was updated successfully, but these errors were encountered: