-
Notifications
You must be signed in to change notification settings - Fork 398
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
error: inlining failed in call to 'always_inline' '_mm256_cvtph_ps': target specific option mismatch #48
Comments
I have the same problem. |
I've noticed that the errors refer to /usr/local/lib/gcc of which doesn't exist for me, but gcc and build-essentials are installed. |
This issue seems to arise while compiling https://github.com/ggerganov/llama.cpp from source. It seems like the simple solution here would be to simply use the prebuilt Docker image from that repo as a build step as opposed to compiling from source. |
I've opened a PR that should address this issue using the method outlined in my previous comment. I've run this locally with no issues since it circumvents the need for compiling entirely. |
I'm sorry for not understanding but what is done with the repository that you located in your other comment |
Seems related to ggerganov/llama.cpp#196 and by extension ggerganov/llama.cpp#535. I tweaked the VMware EVC CPU Mode to "Haswell" in my environment and was able to complete the compilation. |
Hey everyone! If that's still an issue, anyone willing to try out the changes in the following PR: #109 This should hopefully fix things, by switching to llama-rs. Just do:
|
I deployed this PR as a test and I'm still running into it on my Dell PowerEdge R620, but I believe it doesn't support the AVX instruction set so this may be moot as far as it is concerned. I can test deploy on my known working setup of Ubuntu VM on MacBook if you need. |
@willjasen did you figured out the issue? |
Hi!
Sorry to make this an issue, but I'm running into it! I've followed the README and am trying to get it running but I run into quite a few errors. Maybe I'm just missing a dependency or something like that, but I haven't quite figured it out for myself yet and am wondering if others might be running into the same thing? I've tried this on two fairly clean Ubuntu 22.04 machines with the same results.
After the initial docker stuff does its pulls, I run into these lines of output:
The text was updated successfully, but these errors were encountered: