-
-
Notifications
You must be signed in to change notification settings - Fork 325
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
Could not build Taskwarrior 3.0.2 #3605
Comments
What version of rust are you using? Typically the system packages are long out of date. The current minimum version is 1.70.0. It's generally best to use |
To be completely sure I cleaned up rust toolchain and reinstalled via rustup. Now I have rustc 1.80.1 (3f5fd8dd4 2024-08-06) and the same issue stated above |
3.0.2 actually doesn't work with the new rust - #3485 fixed a bug around I don't know what's up with the failures to build |
Good, 3.1.0 works just fine, thanks!
I didn't see any reference to rust version (nor to rust actually) in the INSTALL file. |
Well, it was released before the new rust version was, so that information was as yet unknown :) |
I'm sorry, I've been unclear. What I meant was that the dependency section does not list rust in any way, while it lists make, gcc, clang, etc. |
Oh, good point - I've filed #3606 to fix that. Did you figure out the issue building the Taskchampion dependencies? |
Can confirm I had the same issue, and moving to taskwarrior 3.1.0 resolved my issues. |
Cool, sounds like this is fixed then |
No, I couldn't understand what the problem was, nor how to fix it |
Can you give the version of rust and the commit hash of taskchampion you are building? |
I might have created some misunderstanding. Once I got 3.1.0 working, I didn't continue debugging the original issue |
OK, as long as the most recent version is building 👍🏼 |
To report a bug...
I downloaded Taskwarrior 3.0.2 and follow the instructions in
INSTALL
file, and it ended with errorI tried to build taskchampion manually, but it also failed
The text was updated successfully, but these errors were encountered: