-
Notifications
You must be signed in to change notification settings - Fork 11.9k
Bug: Renaming of executables breaks tutorials #8397
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
Comments
Yes, I understand that, that's fine. All I am asking for is a reasonable, useful error message when someone tries to run "Error: ./main has been renamed to ./llama-cli; please update your scripts and documentation" (and similarly for |
For the most part this should have been addressed in #8283 |
A project that fixes problems by the time I can even report them? Nice! Thanks! |
One change we made in #8283 was to make it so that it only builds the replacement
However, because it doesn't always build the binaries, then this won't help for people who are following a tutorial and typing in |
I just opened a PR (#8404) to build the name-migration-alert
Are there tutorials that you've seen that instruct people to run |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
What happened?
I was getting started with llama.cpp and the existing tutorials all say to run
./main
and./server
, which have very recently (1c641e6, 2024-06-12) been renamed to./llama-cli
and./llama-server
(as I understand it).Could you please (temporarily) restore the old names, and deprecate them instead— by adding shell scripts with the old names that announce the deprecation and run the new executable with the same arguments? Even just announcing the new name and quitting would be helpful.
While I eventually figured this out, it is a frustrating stumbling block for new users (and possibly existing ones, as well).
Name and Version
Note: I downloaded the source, version
b3334
, and built it myself.What operating system are you seeing the problem on?
Mac
Relevant log output
The text was updated successfully, but these errors were encountered: