-
-
Notifications
You must be signed in to change notification settings - Fork 844
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Error making wezterm-git when updating from AUR #3020
Comments
Can you try with a newer version of rust? Sounds like we'll need to update the min supported version |
Using rustc 1.67.0 instead of 1.66.1-2 did the job. I managed to update this from source and directly from the AUR (just to be sure), but had to install the latest version available in the Rust's webpage first. The Thanks! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Build Environment (please complete the following information):
OS:
Linux X11
LSB Version: n/a
Distributor ID: EndeavourOS
Description: EndeavourOS Linux
Release: rolling
Codename: rolling
Linux:
EndeavourOS:
Linux 6.1.8-arch1-1 build issue with harfbuzz #1 SMP PREEMPT_DYNAMIC Tue, 24 Jan 2023 21:07:04 +0000 x86_64 GNU/Linux
Compiler:
gcc version 12.2.1 20230111 (GCC)
Rust version:
stable-x86_64-unknown-linux-gnu (default)
rustc 1.64.0 (a55dd71d5 2022-09-19)
Dependencies
Did you run the
get-deps
script to install required system dependencies?Was it successful?
R/ Yes. Successful installation.
$OSTYPE is linux-gnu
was the final output.If building from the git repo, did you update the submodules? Not doing this
is a common source of problems; see the information at
https://wezfurlong.org/wezterm/install/source.html for more information.
R/ Yes, I did update the submodules but still throwing errors.
The build output
Please include the output from running the build command:
cargo build --release
The text was updated successfully, but these errors were encountered: