-
Notifications
You must be signed in to change notification settings - Fork 11.4k
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
commit 96ea727
breaks compilation in Windows
#74
Comments
96ea727
breaks compilation in Windows
96ea727
breaks compilation in Windows96ea727
](https://github.com/ggerganov/llama.cpp/commit/96ea727f4780620b60c1897b538654931411a3fd) breaks compilation in Windows
96ea727
](https://github.com/ggerganov/llama.cpp/commit/96ea727f4780620b60c1897b538654931411a3fd) breaks compilation in Windows96ea727
breaks compilation in Windows
Oh my god, I'm sorry for all the edits, I thought links on the titles were supported, lol |
blackhole89
added a commit
that referenced
this issue
Mar 13, 2023
I #if-gated the signals-related stuff (which I figure would not work on Windows). As for ANSI colors, I figure you can always just not pass |
I confirm that the commit a169bb8 fixes this issue! |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sadly, Windows terminal support of ANSI colors and signals is simply... non-existent, and this PR in particular adds a ton of things that are not supported by this OS.
I don't know if filling the entire llama.cpp with
#ifdef
s would be ideal... or to rewrite those changes to encapsulate them better to make it less painful, but either way, it is a lot of work.Reverting that commit and doing a couple of merge fixes makes it work.
PS: Maybe it would be good to add an action that compiles the software in the three platforms? but, yet, I'm curious about the willing to support windows as well since it's the special kid between the unix-like guys :)
The text was updated successfully, but these errors were encountered: