-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Shared library with base name 'llama' not found, windows #30
Comments
Hey @Mohamedballouch can you let me know the contents of the |
Hey man @abetlen , no dll in the folder |
So this seems to be an issue with anaconda, I'll have to investigate, if it's possible I'd recommend using a different package manager (pip or poetry should both work). Alternatively you can build the .dll and copy it into the folder above
|
Same on pip installation |
Facing the same issue on windows, I tried on WSL and it moves past this error but the process gets killed because I don't have enough RAM for WSL + 13B llama... Would appreciate it if there was a way to get this to work on native windows... Thanks. |
Sorry, I think the
@viktor02 can you try that as well, that might be why the function isn't being linked in properly. |
Your suggestion worked for me but instead of |
Thank you, it's working |
I just went through same process that people are having issues with while getting oobabooga/text-generation-webui setup and noticed It looks like the pip install process generates the |
Yeah if you check the github actions tab I'm currently struggling through this one too lol. Checking the cmake logs it looks like it gets built but not placed in the same place as other platforms? But I'd assume this line should handle that, no? |
@abetlen
By adding the runtime destination to the cmake config it correctly places the dll on windows. On Windows, shared libraries are typically installed in the bin directory, whereas on Unix-like systems, they are installed in the lib directory. So that's why it ended up in bin. |
Dude, for real. I can't imagine trying to troubleshoot a weird python/windows discrepancy from workflows 💀 Okay, so now it can find the lib, but I don't know the best way to streamline the build process. A lot of people are going to have this auto-configured environment, and it has lots of packages, so we might be able to follow one of those packages approaches for setting up builds. https://github.com/oobabooga/one-click-installers/blob/oobabooga-windows/install.bat I'm not really familiar with getting build environments setup from python. |
can someone advise me on this issue, windows
from .llama_cpp import * File "C:\Users\usr1\Anaconda3\envs\chatgpt1\lib\site-packages\llama_cpp\llama_cpp.py", line 46, in
_lib = _load_shared_library(_lib_base_name)
File "C:\Users\moham\Anaconda3\envs\chatgpt1\lib\site-packages\llama_cpp\llama_cpp.py", line 40, in _load_shared_library
raise FileNotFoundError(f"Shared library with base name '{lib_base_name}' not found")
FileNotFoundError: Shared library with base name 'llama' not found
The text was updated successfully, but these errors were encountered: