-
Notifications
You must be signed in to change notification settings - Fork 690
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
uv pip install
fails to install llama-cpp-python
#6030
Comments
Uhm, I cannot decipher the last line:
There might be another version of ggml-alloc somewhere in the machine? |
Thank you very much for your answer @baggiponte |
I tested other versions of llama-cpp-python. Up to version |
I can take a look. My guess is we're refusing to overwrite a file with a symlink, or something like that. |
I think there might be something wrong with this source distribution. If you untar it, every entry is duplicated:
I don't see the same issue with the prior release. Do you mind reporting this on the library itself? |
Nevermind, I commented on abetlen/llama-cpp-python#1670. |
scikit-build-core 0.10.2 should fix this (thanks to @abetlen)! |
Great. Thank you very much. Should I close it then or leave it open until fixed in case other people are having the same issue? |
Best to close it so we know we don't need to do anything here. Thanks! |
For others looking at this issue, this has been solved in |
Thank you very much for this package. I'm encountering the following issue. In an emptly virtual environment, when I run
uv pip install llama-cpp-python --verbose
I obtain
Current uv version: uv 0.2.35
Current platform:
PRETTY_NAME="Ubuntu 22.04.4 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.4 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy
The text was updated successfully, but these errors were encountered: